Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-0315 is a high-severity Command Injection (CWE-77) vulnerability in Froxlor Froxlor. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 0.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-0315 is a command injection vulnerability, tracked as CWE-77, that affects the Froxlor web hosting control panel in versions prior to 2.0.8. The flaw resides in the GitHub repository froxlor/froxlor and received a CVSS 3.1 score of 8.8, reflecting network-accessible exploitation with low attack complexity and low required privileges.
An authenticated attacker with low-privileged access can supply crafted input that results in arbitrary command execution on the underlying host. Successful exploitation grants the attacker full control over confidentiality, integrity, and availability of the affected system, enabling outcomes such as remote code execution without user interaction.
Publicly available proof-of-concept exploits targeting versions 2.0.6 and 2.0.3 have been posted to Packet Storm, and a fix was merged in commit 090cfc26f2722ac3036cc7fd1861955bc36f065a. The associated huntr.dev report confirms the issue was disclosed through coordinated vulnerability handling, indicating that administrators should upgrade to 2.0.8 or later to eliminate the injection vector. The EPSS score has remained elevated near its peak of 0.9032.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0448
Vulnerability Data
Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
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.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
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.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.