{
  "id": "cve-2026-76208",
  "title": "phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP",
  "product": "phpMyFAQ",
  "ai_system": "AISLE AI-native discovery engine (specific model not identified)",
  "organization": "AISLE (self-attributed AI-engine discovery); VulnCheck CNA record",
  "summary": "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.",
  "ai_role": "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.",
  "disclosure_date": "2026-08-19",
  "ai_attribution_date": null,
  "classification": "disclosure",
  "classification_note": "The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.",
  "cves": [
    "CVE-2026-76208"
  ],
  "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/76xxx/CVE-2026-76208.json",
  "ai_source_url": "https://aisle.com/cve-discoveries/",
  "remediation": "fix documented",
  "remediation_note": "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.",
  "advisory_url": "https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234",
  "checked_date": "2026-11-17",
  "cvss": [
    {
      "cve": "CVE-2026-76208",
      "version": "4.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",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/76xxx/CVE-2026-76208.json",
      "source_name": "CVE Program CNA record",
      "checked_date": "2026-11-17"
    },
    {
      "cve": "CVE-2026-76208",
      "version": "3.1",
      "score": 8.2,
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/76xxx/CVE-2026-76208.json",
      "source_name": "CVE Program CNA record",
      "checked_date": "2026-11-17"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-76208"
      ],
      "consequences": [
        "data modification",
        "authentication bypass"
      ],
      "conditions": "phpMyFAQ: 3.1.0 <= 4.1.6 affected",
      "exploitation": "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.",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/76xxx/CVE-2026-76208.json",
      "checked_date": "2026-11-17"
    }
  ]
}
