PoC Monitor
← All CVEs
CVE-2026-75918published 19 Aug 2026 14:01 UTCData: JSON · API

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

Timeline

Days relative to CVE publication
t=0+14+28+42+56+70+84CVE published19 Aug 2026 · t = 0First public PoC17 Nov 2026 · t+90d

First 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.
SourceTitlePublishedFound by us
nuclei templatenuclei template: phpMyFAQ < 4.1.7 - Password Reset Token Exposure via Public Tracking File17 Nov 202618 Nov 2026