Thorsten phpMyFAQ
phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File
phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over user accounts.
First public PoC
90 daysafter publication · 17 Nov 2026 · nuclei template
Public PoCs10 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS8.8high · scored by CNA · CWE-200
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
thorsten phpMyFAQ
- < 4.1.7
Fixed in 4.1.7
Mitigation
Upgrade phpMyFAQ to 4.1.7 or later.
References
- Vendor advisory github.com/thorsten/phpMyFAQ/security/advisori…
Timeline
Days relative to CVE publicationFirst public PoC 90 days after publication; not in CISA KEV. First PoC: nuclei template: phpMyFAQ < 4.1.7 - Password Reset Token Exposure via Public Tracking File (nuclei template, 17 Nov 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: phpMyFAQ < 4.1.7 - Password Reset Token Exposure via Public Tracking File | 17 Nov 2026 | 18 Nov 2026 |