Account takeover via reset tokens in tracking files
Published Aug 19, 2026 · Updated Aug 25, 2026
Information exposure in phpMyFAQ before 4.1.7 allows remote attackers to take over accounts via publicly readable tracking files. UserSession::userTracking() writes the raw reset-link query string, including the u, exp, and sig values, to a dated file inside the web root without access controls. Exploitation requires user tracking, enabled by the installer by default, and a target to open a valid reset link before the token expires or the password changes.
Summary
What happened
Information exposure in phpMyFAQ before 4.1.7 allows remote attackers to take over accounts via publicly readable tracking files. UserSession::userTracking() writes the raw reset-link query string, including the u, exp, and sig values, to a dated file inside the web root without access controls. Exploitation requires user tracking, enabled by the installer by default, and a target to open a valid reset link before the token expires or the password changes.
The record
- CVE
- CVE-2026-75918
- Published
- Aug 19, 2026
- Updated
- Aug 25, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream tracking-file reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo