CVE-2026-76208

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. No fix on record yet. Sources: github.
generic

phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP | Advisories | VulnCheck

https://www.vulncheck.com/advisories/phpmyfaq-through-authentication-bypass-via-ldap
githubMentions a patch (unverified)🟡 PoC Available

029 LDAP login silently reactivates blocked local accounts without logging the state change · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8pr3-q3cw-q234

Vendor Advisories for CVE-2026-76208(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 106× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 193 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-08 08:36 UTCEG score recompute
  4. 2026-10-08 08:36 UTCGHSA enrichment
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-07 06:33 UTCGHSA enrichment
  7. 2026-10-06 19:23 UTCEG score recompute
  8. 2026-10-06 19:23 UTCGHSA enrichment
  9. 2026-10-06 15:18 UTCEPSS rescore
  10. 2026-10-06 08:00 UTCEG score recompute
  11. 2026-10-06 08:00 UTCGHSA enrichment
  12. 2026-10-05 17:43 UTCEPSS rescore
  13. 2026-10-05 17:11 UTCGHSA enrichment
  14. 2026-10-05 05:13 UTCEG score recompute
  15. 2026-10-05 05:13 UTCGHSA enrichment
  16. 2026-10-04 23:22 UTCEPSS rescore
  17. 2026-10-04 15:43 UTCGHSA enrichment
  18. 2026-10-04 04:07 UTCGHSA enrichment
  19. 2026-10-03 16:58 UTCEG score recompute
  20. 2026-10-03 16:58 UTCGHSA enrichment
  21. 2026-10-03 14:26 UTCEPSS rescore
  22. 2026-10-02 21:38 UTCEG score recompute
  23. 2026-10-02 21:38 UTCGHSA enrichment
  24. 2026-10-02 09:56 UTCGHSA enrichment
  25. 2026-10-01 22:48 UTCEG score recompute
Show 75 more
  1. 2026-10-01 22:48 UTCGHSA enrichment
  2. 2026-10-01 19:50 UTCEPSS rescore
  3. 2026-10-01 05:49 UTCGHSA enrichment
  4. 2026-09-30 18:42 UTCEG score recompute
  5. 2026-09-30 18:42 UTCGHSA enrichment
  6. 2026-09-30 17:38 UTCEG score recompute
  7. 2026-09-30 17:38 UTCGHSA enrichment
  8. 2026-09-30 08:50 UTCEG score recompute
  9. 2026-09-30 08:50 UTCGHSA enrichment
  10. 2026-09-29 15:24 UTCEPSS rescore
  11. 2026-09-29 08:53 UTCGHSA enrichment
  12. 2026-09-28 21:44 UTCEG score recompute
  13. 2026-09-28 21:44 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 05:21 UTCGHSA enrichment
  16. 2026-09-27 18:14 UTCEG score recompute
  17. 2026-09-27 18:14 UTCGHSA enrichment
  18. 2026-09-27 13:48 UTCEPSS rescore
  19. 2026-09-27 07:07 UTCEG score recompute
  20. 2026-09-27 07:07 UTCGHSA enrichment
  21. 2026-09-26 15:59 UTCEPSS rescore
  22. 2026-09-26 00:28 UTCEPSS rescore
  23. 2026-09-25 06:57 UTCGHSA enrichment
  24. 2026-09-24 19:49 UTCEG score recompute
  25. 2026-09-24 19:49 UTCGHSA enrichment
  26. 2026-09-24 14:04 UTCEPSS rescore
  27. 2026-09-24 07:17 UTCGHSA enrichment
  28. 2026-09-23 20:10 UTCEG score recompute
  29. 2026-09-23 20:10 UTCGHSA enrichment
  30. 2026-09-23 17:54 UTCEPSS rescore
  31. 2026-09-23 07:05 UTCGHSA enrichment
  32. 2026-09-22 19:58 UTCEG score recompute
  33. 2026-09-22 19:58 UTCGHSA enrichment
  34. 2026-09-22 16:01 UTCEPSS rescore
  35. 2026-09-22 06:24 UTCEG score recompute
  36. 2026-09-22 06:23 UTCGHSA enrichment
  37. 2026-09-21 21:09 UTCEPSS rescore
  38. 2026-09-21 19:16 UTCGHSA enrichment
  39. 2026-09-21 08:08 UTCGHSA enrichment
  40. 2026-09-20 21:00 UTCEG score recompute
  41. 2026-09-20 21:00 UTCGHSA enrichment
  42. 2026-09-20 20:16 UTCEPSS rescore
  43. 2026-09-20 09:53 UTCGHSA enrichment
  44. 2026-09-19 22:44 UTCEG score recompute
  45. 2026-09-19 22:44 UTCGHSA enrichment
  46. 2026-09-19 11:21 UTCGHSA enrichment
  47. 2026-09-19 00:14 UTCEG score recompute
  48. 2026-09-19 00:13 UTCGHSA enrichment
  49. 2026-09-18 19:28 UTCEPSS rescore
  50. 2026-09-18 13:06 UTCGHSA enrichment
  51. 2026-09-18 01:56 UTCEG score recompute
  52. 2026-09-18 01:56 UTCGHSA enrichment
  53. 2026-09-17 14:49 UTCGHSA enrichment
  54. 2026-09-17 03:33 UTCGHSA enrichment
  55. 2026-09-16 15:52 UTCEG score recompute
  56. 2026-09-16 15:52 UTCGHSA enrichment
  57. 2026-09-16 14:08 UTCEPSS rescore
  58. 2026-09-16 05:15 UTCEPSS rescore
  59. 2026-09-16 04:45 UTCGHSA enrichment
  60. 2026-09-15 17:36 UTCGHSA enrichment
  61. 2026-09-15 06:26 UTCEG score recompute
  62. 2026-09-15 06:26 UTCGHSA enrichment
  63. 2026-09-15 03:12 UTCEPSS rescore
  64. 2026-09-14 19:18 UTCGHSA enrichment
  65. 2026-09-14 07:17 UTCGHSA enrichment
  66. 2026-09-13 20:10 UTCEG score recompute
  67. 2026-09-13 20:10 UTCGHSA enrichment
  68. 2026-09-13 09:02 UTCGHSA enrichment
  69. 2026-09-12 21:55 UTCEG score recompute
  70. 2026-09-12 21:55 UTCGHSA enrichment
  71. 2026-09-12 15:02 UTCEPSS rescore
  72. 2026-09-12 10:47 UTCGHSA enrichment
  73. 2026-09-11 23:36 UTCEG score recompute
  74. 2026-09-11 23:36 UTCGHSA enrichment
  75. 2026-09-11 14:53 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76208?
CVE-2026-76208 is a high vulnerability published on August 19, 2026. 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…
When was CVE-2026-76208 disclosed?
CVE-2026-76208 was first published on August 19, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76208 actively exploited?
CVE-2026-76208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76208?
CVE-2026-76208 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76208?
No fix for CVE-2026-76208 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-76208 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76208

Explore →

Is Your Infrastructure Affected by CVE-2026-76208?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs