CVE-2026-75918

published 19 Aug 2026 · updated 25 Aug 2026

phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File

9.8CriticalCVSS 8.8EPSS 1%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 4.1.7.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
thorsten<4.1.74.1.7

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-75918 severity on Zeptric[![CVE-2026-75918](https://zeptric.io/badge/cve/CVE-2026-75918.svg)](https://zeptric.io/cve/CVE-2026-75918)