CVE-2026-76208

Published: Ago 19, 2026 Last Modified: Ago 19, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,8
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
HIGH 8,2
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: low
Integrity: high
Availability: none

Description

AI Translation Available

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.

778

Insufficient Logging

Draft
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Non-Repudiation
Potential Impacts:
Hide Activities
Applicable Platforms
Technologies: Cloud Computing, Not Technology-Specific
Likelihood of Exploit: Medium
View CWE Details
https://github.com/thorsten/phpMyFAQ/security/advisories/GH…
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234
https://www.vulncheck.com/advisories/phpmyfaq-through-authe…
https://www.vulncheck.com/advisories/phpmyfaq-through-authentication-bypass-via…