Vulnerability 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 Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Phpmyfaq | Phpmyfaq | >= 3.1.0, < 4.1.6 |
Related Weaknesses (CWE)
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234ExploitVendor Advisory
- https://www.vulncheck.com/advisories/phpmyfaq-through-authentication-bypass-via-Third Party Advisory
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234ExploitVendor Advisory
FAQ
What is CVE-2026-76208?
CVE-2026-76208 is a vulnerability with a CVSS score of 8.2 (HIGH). 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::setSt...
How severe is CVE-2026-76208?
CVE-2026-76208 has been rated HIGH with a CVSS base score of 8.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-76208?
Check the references section above for vendor advisories and patch information. Affected products include: Phpmyfaq Phpmyfaq.