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.
Published: 2026-08-19
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Bypass
Action: Patch Now
AI Analysis

Impact

phpMyFAQ versions 3.1.0 through 4.1.6 contain a flaw in AuthLdap::create() that, after a successful LDAP bind, unconditionally sets a local account status to active. This overwrites a blocked account, allowing a user whose local phpMyFAQ account has been administratively blocked to regain access via LDAP. No audit log entry is produced for the state transition, so the restoration can occur without administrative notice.

Affected Systems

Affecting deployments running phpMyFAQ 3.1.0 through 4.1.6 with LDAP authentication enabled, any user mapped via LDAP to a locally blocked account is vulnerable until the system is updated to version 4.1.7 or later.

Risk and Exploitability

The vulnerability scores 8.8 on the CVSS scale, indicating high severity, and it is not listed in the CISA KEV catalog. The EPSS score is below 1%, indicating a very low probability of exploitation in the wild. Based on the description, it is inferred that exploitation most likely occurs over the web interface by authenticating via LDAP; the attacker would need LDAP access to the target account and can trigger the status change silently, resulting in unauthorized access without detection.

Generated by OpenCVE AI on August 20, 2026 at 16:36 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.7 or newer.
  • If an immediate upgrade is not feasible, temporarily disable LDAP authentication or configure the LDAP component to prevent automatic status changes for blocked local accounts.
  • Implement monitoring or auditing of the account_status field so that any unauthorized status changes can be detected and investigated.

Generated by OpenCVE AI on August 20, 2026 at 16:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 01 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*

Thu, 20 Aug 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq

Wed, 19 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 19 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
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.
Title phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-778
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:-:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N'}

cvssV4_0

{'score': 8.8, 'vector': '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'}


Subscriptions

Phpmyfaq Phpmyfaq
Thorsten Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-19T15:12:14.681Z

Reserved: 2026-08-19T11:34:28.576Z

Link: CVE-2026-76208

cve-icon Vulnrichment

Updated: 2026-08-19T15:11:29.426Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-19T14:17:46.220

Modified: 2026-09-01T15:22:46.917

Link: CVE-2026-76208

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T16:45:16Z

Weaknesses