Security readout for executives and security teams
Plain-English summary
CVE-2023-0788 is a high-severity code injection flaw in thorsten/phpmyfaq before 3.1.11. A low-privileged authenticated attacker could potentially cause unauthorized code execution effects, creating serious confidentiality and integrity risk. The sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Prioritize remediation for exposed or externally authenticated phpMyFAQ deployments. This is not marked as known exploited, but the impact profile supports prompt patching because confidentiality and integrity consequences are high.
Technical view
The CVE describes CWE-94 code injection in thorsten/phpmyfaq prior to 3.1.11. CVSS 3.1 is 8.1: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure is limited to organizations running phpMyFAQ versions before 3.1.11. Risk is higher for internet-accessible deployments where untrusted or lightly trusted users can authenticate. The source bundle does not provide more granular affected version details.
Exploitation context
The bundle includes a Huntr reference tagged as exploit, but no exploit details are needed for validation. CISA KEV is false, and the provided sources do not document active exploitation in the wild.
Researcher notes
Sources identify code injection but provide limited product-version granularity beyond prior to 3.1.11. Validation should focus on version confirmation, authentication exposure, and evidence of abnormal application changes rather than attempting reproduction in production.
Mitigation direction
- Upgrade phpMyFAQ to version 3.1.11 or later.
- Review the vendor commit and release guidance for the exact fix.
- Restrict access to authenticated phpMyFAQ functions until upgraded.
- Remove unnecessary low-privileged accounts from exposed deployments.
- Monitor affected instances for suspicious content or configuration changes.
Validation and detection
- Inventory all phpMyFAQ instances and record their versions.
- Confirm whether any instance is older than 3.1.11.
- Identify internet-facing deployments and authentication paths.
- Review application logs for unexpected authenticated changes.
- Check whether compensating access controls are active.
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-0788 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/808d5452-607c-4af1-812f-26c49faf3e61CVE reference
- https://github.com/thorsten/phpmyfaq/commit/77b42b9d0be3990ee7389207a71528b304b03039CVE reference
- https://huntr.com/bounties/808d5452-607c-4af1-812f-26c49faf3e61CVE 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 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.