CVE-2026-76208
CVE-2026-76208 is a high-severity vulnerability with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-778.
Key facts
- Severity: High (CVSS 3.x base score 8.2)
- CVSS v4: 8.8
- EPSS exploit prediction: 0% (17th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-778
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-76208?
- 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.
- How severe is CVE-2026-76208?
- CVE-2026-76208 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability none.
- Is CVE-2026-76208 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-76208?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-76208 published?
- CVE-2026-76208 was published on 2026-08-19.
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234
- https://www.vulncheck.com/advisories/phpmyfaq-through-authentication-bypass-via-ldap
Other CWE-778 vulnerabilities
- CVE-2024-48967 — Critical (CVSS 10.0): The ventilator and the Service PC lack sufficient audit logging capabilities to allow for detection of malicious…
- CVE-2021-43419 — High (CVSS 7.5): An Information Disclosure vulnerability exists in Opay Mobile application 1.5.1.26 and maybe be higher in the logcat…
- CVE-2019-7613 — High (CVSS 7.5): Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw. An attacker able to inject certain…
- CVE-2019-19277 — Medium (CVSS 6.5): A vulnerability has been identified in SIPORT MP (All versions < 3.1.4). Vulnerable versions of the device allow the…
- CVE-2025-52644 — Medium (CVSS 5.8): HCL AION is affected by a vulnerability where certain user actions are not adequately audited or logged. The absence of…
- CVE-2025-62307 — Medium (CVSS 5.4): HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability,…