Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Phpmyfaq | Phpmyfaq | < 4.1.7 |
Related Weaknesses (CWE)
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j5w2-cwwj-xj7xExploitVendor Advisory
- https://www.vulncheck.com/advisories/phpmyfaq-before-authentication-bypass-via-tThird Party Advisory
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j5w2-cwwj-xj7xExploitVendor Advisory
FAQ
What is CVE-2026-75918?
CVE-2026-75918 is a vulnerability with a CVSS score of 8.8 (HIGH). 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/track...
How severe is CVE-2026-75918?
CVE-2026-75918 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-75918?
Check the references section above for vendor advisories and patch information. Affected products include: Phpmyfaq Phpmyfaq.