CVE-2026-76208Network attack vector

Blocked-account access via LDAP reactivation

Published Aug 19, 2026 · Updated Aug 19, 2026

Authentication bypass in phpMyFAQ 3.1.0 through 4.1.6 allows remote attackers to regain blocked account access via LDAP login. In AuthLdap::create(), a successful LDAP bind unconditionally calls User::setStatus('active'), overwriting account_status for an existing local user instead of preserving an administrator-set blocked state. Reachability requires LDAP authentication to be enabled and the attacker to know valid LDAP credentials for a previously blocked local account; the reactivation is not audit-logged, so the access restoration can evade administrative notice.

CVSS severity8.8
High
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in phpMyFAQ 3.1.0 through 4.1.6 allows remote attackers to regain blocked account access via LDAP login. In AuthLdap::create(), a successful LDAP bind unconditionally calls User::setStatus('active'), overwriting account_status for an existing local user instead of preserving an administrator-set blocked state. Reachability requires LDAP authentication to be enabled and the attacker to know valid LDAP credentials for a previously blocked local account; the reactivation is not audit-logged, so the access restoration can evade administrative notice.

The record

CVE
CVE-2026-76208
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Thorsten Rinne
Product
phpMyFAQ
Classifications
CWE-778, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Thorsten Rinne · phpMyFAQAffected versions are unavailable in this record.

Published CVSS scores

8.8GitHub Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
8.2CVE recordCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-778Insufficient Logging
T1078Valid Accounts

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo