phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File (CVE-2026-75918) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-75918

phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File

Answer in brief

CVE-2026-75918 records a Unknown severity vulnerability in phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File. The current sources do not mark it as known exploited. The current feed maps thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
thorsten/phpMyFAQgeneric	>=0 <4.1.7	4.1.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for thorsten/phpMyFAQ.
Review the reported fix. Update thorsten/phpMyFAQ to 4.1.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.