Authenticated 2FA bypass via premature persistent token
Published Aug 19, 2026 · Updated Aug 25, 2026
Authentication bypass in phpMyFAQ before 4.1.7 allows remote authenticated users to access 2FA-protected accounts without a second factor. The login routine issues a persistent authentication token after password validation but before 2FA completes, and the cookie lookup accepts that token without checking 2FA status. Valid primary credentials and persistent-login selection are required; replaying the cookie grants the account's full authenticated access.
Summary
What happened
Authentication bypass in phpMyFAQ before 4.1.7 allows remote authenticated users to access 2FA-protected accounts without a second factor. The login routine issues a persistent authentication token after password validation but before 2FA completes, and the cookie lookup accepts that token without checking 2FA status. Valid primary credentials and persistent-login selection are required; replaying the cookie grants the account's full authenticated access.
The record
- CVE
- CVE-2026-76207
- Published
- Aug 19, 2026
- Updated
- Aug 25, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-304, T1078
- Attack vector
- network
- Privileges
- authenticated
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.
Public exploit references
No public exploit references are available in this record.
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