CVE-2026-75918 phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File
Unauthenticated attackers can take over user accounts by reading password reset tokens from a publicly accessible tracking file when user tracking is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-75918?
CVE-2026-75918 is a high-severity authentication bypass vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-200
Which versions are affected by CVE-2026-75918?
It affects 1 product.
Products include Phpmyfaq Phpmyfaq.
How do I fix CVE-2026-75918?
No fix has been published for CVE-2026-75918 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-75918 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75918 exists.
Other vulnerabilities in Phpmyfaq Phpmyfaq
- CVE-2023-0310 Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq
- CVE-2022-4407 Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq
- CVE-2017-11187 Security feature bypass in n/a
- CVE-2026-76213 phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle
- CVE-2026-76214 phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge
Sources
Also known as GHSA-hccc-74hg-j43v, GHSA-j5w2-cwwj-xj7x.