CVE-2026-76206: thorsten phpMyFAQ · Information Exposure
Affects thorsten phpMyFAQSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.1.7 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threats | Affected
| Fixed in
|
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 the issue is fixed by proper validation of FAQ active status in the PDF export endpoint. No other mitigation is indicated or necessary once the official fix is applied.
Description
phpMyFAQ versions prior to 4.1.7 contain a vulnerability in the PDF export endpoint that allows unauthenticated attackers to access draft FAQ metadata. This occurs because the application fails to validate the active status of FAQs, enabling retrieval of titles, solution IDs, author names, and last-update timestamps for inactive or unpublished FAQs via sequential FAQ identifiers.