CVE•Published 2026-08-19•Modified 2026-11-20•1 article on news•5 live references•NVD data

CVE-2026-76208Phpmyfaq · Phpmyfaq

Vulnerability data via NVD (ingested)

CVSS v3.1
8.2
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS percentile
39
Exploit Prediction Scoring System · top 61% of all CVEs
Description

phpMyFAQ versions 3.1.0 before 4.1.7 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.

Timeline
Published 2026-08-19
Modified 2026-11-20

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-76208 on GitHub.