CVE-2026-76208: Insufficient Logging in thorsten phpMyFAQ
Description
phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create(). When LDAP authentication is enabled, after a successful LDAP bind the code calls User::setStatus('active') unconditionally, which overwrites the account_status column of a pre-existing local account from 'blocked' to 'active'. As a result, a user whose local phpMyFAQ account has been administratively blocked can restore their account and log in by authenticating via LDAP. The state transition is not logged, so administrators cannot detect that the block was overridden. Fixed in 4.1.7.
CVSS v4.0
Score 8.8high
Affected software
thorsten
phpMyFAQ
pkg:github/thorsten/phpMyFAQRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76208 describes an authentication bypass vulnerability in phpMyFAQ's AuthLdap::create() function affecting versions 3.1.0 through 4.1.6. When LDAP authentication is enabled, after a successful LDAP bind, the code calls User::setStatus('active') unconditionally, overwriting the 'blocked' status of a local account to 'active'. This enables a user with a previously blocked local account to restore access by authenticating through LDAP. Additionally, this state transition is not logged, preventing administrators from detecting that the block was overridden. The vulnerability is resolved in phpMyFAQ version 4.1.7.
Potential Impact
The vulnerability allows users with administratively blocked local accounts to bypass the block and regain access by authenticating via LDAP. Because the status change from 'blocked' to 'active' is not logged, administrators cannot detect that the block was overridden, potentially allowing unauthorized access without audit trails. This poses a high security risk to affected systems.
Mitigation Recommendations
Upgrade phpMyFAQ to version 4.1.7 or later, where this vulnerability is fixed. Until then, administrators should be aware that blocked accounts may be reactivated via LDAP authentication without logging. No other mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:34:28.576Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a85bc76acd9273b492f497e
Added to database: 08/19/2026, 14:23:50 UTC
Last enriched: 10/01/2026, 15:43:26 UTC
Last updated: 10/04/2026, 10:09:59 UTC
Views: 35
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.