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.
References
| Link | Resource |
|---|---|
| https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j5w2-cwwj-xj7x | Exploit Vendor Advisory |
| https://www.vulncheck.com/advisories/phpmyfaq-before-authentication-bypass-via-tracking-file | Third Party Advisory |
| https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j5w2-cwwj-xj7x | Exploit Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-08-19 14:17
Updated : 2026-09-01 15:30
NVD link : CVE-2026-75918
Mitre link : CVE-2026-75918
CVE.ORG link : CVE-2026-75918
JSON object : View
Products Affected
phpmyfaq
- phpmyfaq
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
