Security readout for executives and security teams
Plain-English summary
Older phpMyFAQ deployments may let a logged-in, low-privileged user inject operating-system commands. The main business risk is data exposure or unauthorized changes in the application environment. The source bundle names versions before 3.1.11 as affected.
Executive priority
Prioritize remediation in the next patch cycle, faster for public-facing systems or environments with broad user access. The issue can affect confidentiality and integrity, but no source in the bundle confirms active exploitation.
Technical view
CVE-2023-0789 is CWE-77 command injection in thorsten/phpmyfaq before 3.1.11. CVSS 3.1 is 8.1: network reachable, low complexity, low privileges, no user interaction, with high confidentiality and integrity impact and no availability impact.
Likely exposure
Exposure is most likely on internet-accessible or internally reachable phpMyFAQ instances running versions before 3.1.11, especially where non-administrative authenticated users have access. The bundle does not identify affected endpoints or hosting platforms.
Exploitation context
A public huntr reference is tagged as exploit, but the bundle does not show CISA KEV listing or active exploitation evidence. Treat exploitability as plausible because the CVSS vector requires low privileges and no user interaction.
Researcher notes
The available data confirms product, version boundary, CWE, CVSS vector, and a fixing commit reference. It does not provide enough source-grounded detail to name the vulnerable route, parameter, payload, or operational workaround.
Mitigation direction
- Upgrade phpMyFAQ to 3.1.11 or later.
- Review the referenced upstream commit for the exact fixed code path.
- Restrict phpMyFAQ access to trusted authenticated users until patched.
- Check vendor project guidance for any additional hardening steps.
Validation and detection
- Inventory all phpMyFAQ deployments and record their running versions.
- Flag any instance running a version earlier than 3.1.11.
- Confirm patched systems include the upstream fix commit or later release.
- Review application and system logs for suspicious command execution indicators.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-0789 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://huntr.dev/bounties/d9375178-2f23-4f5d-88bd-bba3d6ba7cc5CVE reference
- https://github.com/thorsten/phpmyfaq/commit/40515c74815ace394ab23c6c19cbb33fd49059cbCVE reference
- https://huntr.com/bounties/d9375178-2f23-4f5d-88bd-bba3d6ba7cc5CVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.