Skip to main content
VulnerabilityPublished Updated

CVE-2026-24420: thorsten phpMyFAQ · Improper Access Control

Affects thorsten phpMyFAQSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.0.17 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.0.17.

Affected software

ProductAffectedFixed in
thorstenphpMyFAQAffected
  • <4.0.17
Fixed in
  • 4.0.17
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threatsAffected
  • <4.0.17
Fixed in
  • 4.0.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade phpMyFAQ installations to version 4.0.17 or later where the vulnerability is fixed. If immediate upgrade is not feasible, implement strict access controls on the phpMyFAQ application, including strong authentication mechanisms and monitoring for unusual attachment download activity. Review and audit user permissions to ensure only authorized users have access to sensitive attachments. Employ network segmentation and web application firewalls (WAFs) to restrict access to the phpMyFAQ server. Additionally, consider disabling attachment downloads temporarily if they are not essential. Conduct regular security assessments and penetration tests focusing on access control mechanisms. Educate users on credential security to reduce the risk of compromised accounts that could exploit this vulnerability.

Description

phpMyFAQ is an open source FAQ web application. Versions 4.0.16 and below allow an authenticated user without the dlattachment permission to download FAQ attachments due to a incomprehensive permissions check. The presence of a right key is improperly validated as proof of authorization in attachment.php. Additionally, the group and user permission logic contains a flawed conditional expression that may allow unauthorized access. This issue has been fixed in version

References

Community reviews

Loading reviews…