Security readout for executives and security teams
Plain-English summary
phpMyFAQ before 4.0.17 may let a logged-in user download FAQ attachments even when they lack the required download permission. This is mainly a confidentiality risk: attachments could contain internal documents, customer information, or operational details.
Executive priority
Treat as a near-term patching item if phpMyFAQ stores sensitive attachments. Business urgency is moderate: exploitation requires login, but successful abuse could expose confidential files without changing systems.
Technical view
CVE-2026-24420 is a broken access control issue in phpMyFAQ attachment handling. Versions below 4.0.17 improperly treat the presence of a right key as authorization and include flawed user/group permission logic. CVSS 3.1 is 6.5, with network access, low complexity, low privileges, and high confidentiality impact.
Likely exposure
Organizations running phpMyFAQ versions below 4.0.17 are exposed, especially if authenticated users can access the application and FAQ attachments contain sensitive information.
Exploitation context
Sources indicate exploitation requires an authenticated user and no user interaction. The source bundle does not show CISA KEV listing or other evidence of active exploitation.
Researcher notes
The issue maps to CWE-284 and centers on incomplete authorization checks in attachment.php plus flawed group/user permission logic. The provided sources do not include indicators of compromise, exploit availability, or broader affected products.
Mitigation direction
- Upgrade phpMyFAQ to version 4.0.17 or newer.
- Review vendor advisory guidance for any additional configuration recommendations.
- Limit access to phpMyFAQ accounts until the upgrade is complete.
- Review attachments and remove sensitive files that do not need to be available.
Validation and detection
- Inventory phpMyFAQ deployments and confirm installed versions.
- Verify affected systems are not running versions below 4.0.17.
- Confirm users without dlattachment permission cannot access attachments after remediation.
- Review logs for unexpected attachment downloads by low-privileged users.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2026-24420 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:L/UI:N/S:U/C:H/I:N/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:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-7p9h-m7m8-vhhvCVE reference · x_refsource_CONFIRM
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 Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.