Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2023-0789 is a high-severity Command Injection (CWE-77) vulnerability in Phpmyfaq Phpmyfaq. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 25% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
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-0789 is a command injection vulnerability, tracked as CWE-77, that affects the phpMyFAQ application in the thorsten/phpmyfaq GitHub repository for all versions prior to 3.1.11. The flaw stems from insufficient neutralization of special elements in commands and carries a CVSS 3.1 base score of 8.1 reflecting network attack vector, low complexity, and low required privileges.
An authenticated attacker with low privileges can send crafted input over the network to execute arbitrary system commands, resulting in high impact to confidentiality and integrity on the underlying server while leaving availability unaffected.
The issue was resolved by a specific commit in the repository that patches the command injection path, with the fix publicly referenced in the associated huntr.dev bounty report; administrators should upgrade to phpMyFAQ 3.1.11 or apply the equivalent patch.
EPSS for the CVE has remained flat at 0.0776 with no material rise after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0645
Vulnerability Data
Command Injection in GitHub repository thorsten/phpmyfaq prior to 3.1.11.
- 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.