CVE-2026-76208: phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create(). When LDAP…

CVE-2026-76208 · Severity: high · CVSS 8.2 · Published 2026-08-19

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.

Technologies: Phpmyfaq. Vendors: Phpmyfaq.

Quick answers

Is CVE-2026-76208 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-76208 being exploited in the wild.
How severe is CVE-2026-76208?
High severity, with a CVSS score of 8.2, published 19 August 2026.
Which products and versions are affected?
Phpmyfaq. The advisory does not name versions.
Is there a fix for CVE-2026-76208?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-76208?
Check whether you run Phpmyfaq. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Phpmyfaq

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.