Finding and attribution
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.
Product: phpMyFAQ. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE (self-attributed AI-engine discovery); VulnCheck CNA record.
CVE identifiers: CVE-2026-76208.
AI and human contribution (source account): The primary AISLE CVE-discoveries index explicitly scopes its listed cases as CVEs discovered by its AI-native engine and individually lists CVE-2026-76208. This is AISLE's self-attributed case-specific AI-engine claim. The available sources do not identify a model, establish autonomy or first-discovery priority, or define the human/tool work split.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.
Remediation status: fix documented. The maintainer advisory metadata lists 4.1.7 as patched and its suggested fix guards blocked/protected accounts before setting status active. However, the same advisory body says 4.1.6 was then the latest stable release and “no fix exists in any released version.” Preserve this conflict; do not claim that 4.1.7 was released or that installations are patched.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 19 Aug 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: data modification, authentication bypass.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-76208: CVSS 4.0 · 8.8 (High) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N. CVE Program CNA record · checked 17 Nov 2026. - CVE-2026-76208: CVSS 3.1 · 8.2 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. CVE Program CNA record · checked 17 Nov 2026.
CVE-2026-76208: data modification, authentication bypass.
Prerequisites / affected scope: phpMyFAQ: 3.1.0 <= 4.1.6 affected.
Exploitation evidence: The CNA description establishes the stated technical effect. The checked CNA record does not report exploitation in the wild; no exploitability beyond the description is inferred.. Impact source · checked 17 Nov 2026.
Documented fix: The maintainer advisory metadata lists 4.1.7 as patched and its suggested fix guards blocked/protected accounts before setting status active. However, the same advisory body says 4.1.6 was then the latest stable release and “no fix exists in any released version.” Preserve this conflict; do not claim that 4.1.7 was released or that installations are patched.