Security readout for executives and security teams
Plain-English summary
CVE-2023-0792 is a code injection flaw in thorsten/phpmyfaq before version 3.1.11. A remote unauthenticated attacker may be able to affect limited confidentiality and integrity. The public sources do not show active exploitation or detailed affected deployments.
Executive priority
Treat this as a moderate patching priority, elevated for public-facing knowledge-base systems. There is no source-backed active exploitation signal, but the vulnerability is remotely reachable and unauthenticated.
Technical view
The CVE describes CWE-94 code injection in thorsten/phpmyfaq prior to 3.1.11, with CVSS 3.1 score 6.5. The vector is network reachable, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality and integrity impact. Availability impact is listed as none.
Likely exposure
Exposure is most likely on internet-accessible phpMyFAQ deployments running versions earlier than 3.1.11. The source bundle does not provide CPEs, exact branch ranges, or endpoint-level details.
Exploitation context
CISA KEV status is false in the source bundle, and no cited source states active exploitation. The CVSS vector suggests exploitation could be remote and unauthenticated, but public evidence here is limited.
Researcher notes
The available sources identify product, weakness class, CVSS vector, and a fixing commit. They do not provide complete affected-version metadata, CPEs, exploit status, or safe reproduction detail, so validation should stay version- and patch-state based.
Mitigation direction
- Upgrade phpMyFAQ to version 3.1.11 or later.
- Review vendor release notes and guidance for the official fix.
- Prioritize externally exposed instances before internal-only deployments.
- Restrict public access where phpMyFAQ does not need internet exposure.
Validation and detection
- Inventory all phpMyFAQ instances and record installed versions.
- Flag any deployment running earlier than 3.1.11.
- Confirm the deployed code includes the referenced fixing commit or later release.
- Review recent logs for unusual unauthenticated requests to phpMyFAQ routes.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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 lookupCVE-2023-0792 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Source materials
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 Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.