CVE-2026-76208 (CVSS 8.2)

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.

Is your site exposed to CVE-2026-76208?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

8.2

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

EPSS — Exploit Prediction

0.0025

Probability of exploitation

0.17%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-778 CWE-778

References

Other References

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234 https://www.vulncheck.com/advisories/phpmyfaq-through-authentication-bypass-via-ldap https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234

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. It has a CVSS v3.1 base score of 8.2 (HIGH).

How severe is CVE-2026-76208? +

CVE-2026-76208 has a CVSS v3.1 score of 8.2 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0025, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-76208? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2024-10863

: Insufficient Logging vulnerability in OpenText Secure Content Manager on Windows allows Audit Log Manipulation.This issue affects Secure Content Manager: …

CVE-2024-48967 10.0

The ventilator and the Service PC lack sufficient audit logging capabilities to allow for detection of malicious activity and subsequent …

CVE-2020-37268 6.3

Print Assumptions does not report that a definition was produced while universe checking was disabled when that definition reaches the …

CVE-2025-2562 5.4

Insufficient logging in the autotyping feature in Devolutions Remote Desktop Manager on Windows allows an authenticated user to use a …

CVE-2025-32967 5.4

OpenEMR is a free and open source electronic health records and medical practice management application. A logging oversight in versions …

CVE-2025-62307 5.4

HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability, obscures attack detection, and enables privilege …

CVE-2026-76208