Skip to main content
VulnerabilityPublished Updated

CVE-2026-76215: thorsten phpMyFAQ · Missing Authorization

Affects thorsten phpMyFAQSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.1.7 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 16 Nov 2026.

What to do

Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.7.

Affected software

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

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

AI-suggested

Upgrade phpMyFAQ to version 4.1.7 or later where this authorization issue has been fixed. No other mitigation guidance is provided. Patch status is confirmed by the version boundary indicating the fix in 4.1.7.

Description

phpMyFAQ versions prior to 4.1.7 contain a missing authorization vulnerability where parent FAQ visibility checks are not enforced before returning child resources such as comments and attachments. This allows unauthenticated attackers to access restricted comment text, commenter email addresses, and attachment filenames for FAQ entries they cannot directly access.

References

Community reviews

Loading reviews…