Cyber Resilience

CVE-2025-30091

Published
25 March 2025
Modified
15 April 2026
CVSS Score v4 9.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0075 52th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-30091 is a critical-severity Static Code Injection (CWE-96) vulnerability in Moxiemanager (inferred from references). Its CVSS base score is 9.4 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Tiny MoxieManager PHP before version 4.0.0 contains a remote code execution vulnerability in its installer command. The flaw stems from CWE-96 and permits unauthenticated insertion of attacker-controlled data via InstallCommand directly into the generated config.php file, with the command remaining reachable even after initial setup completes. The issue carries a CVSS 4.0 score of 9.4 reflecting network-accessible, low-complexity exploitation with high impact across confidentiality, integrity, and availability.

An attacker can supply malicious input to InstallCommand to write and execute arbitrary PHP code on the server. Because the endpoint stays available post-installation and requires no authentication, the attack can be launched remotely by any party able to reach the MoxieManager instance, resulting in full compromise of the affected web application and underlying host.

Public advisories and the product changelog at moxiemanager.com address the issue under identifier SEC-1063 and document the availability of version 4.0.0 as the corrective release. The associated EPSS score remains low, with a current value of 0.0140 and a peak of only 0.0168.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

In Tiny MoxieManager PHP before 4.0.0, remote code execution can occur in the installer command. This vulnerability allows unauthenticated attackers to inject and execute arbitrary code. Attacker-controlled data to InstallCommand can be inserted into config.php, and InstallCommand is available after…

more

an installation has completed.

CWE(s)
CWE-96

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1027.009 Embedded Payloads Stealth
Adversaries may embed payloads within other files to conceal malicious content from defenses.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-57707Shared CWE-96
CVE-2024-13264Shared CWE-96
CVE-2025-36595Shared CWE-96
CVE-2024-13267Shared CWE-96
CVE-2024-13268Shared CWE-96
CVE-2024-13265Shared CWE-96
CVE-2024-0788Shared CWE-96
CVE-2024-32487Shared CWE-96
CVE-2025-7825Shared CWE-96
CVE-2023-39726Shared CWE-96

Affected Assets

Moxiemanager
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

SI-10 Information Input Validation good match

Input validation directly stops unneutralized directives from being inserted into static code resources.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

A.8.32 Change management none match
mitigates

Change management can catch unsafe code changes but does not enforce input neutralization.

References