phpMyFAQ before 4.1.7 contains a brute-force vulnerability in the two-factor authentication step where the failure counter is session-scoped and reset on each successful password re-authentication. Attackers with a valid password can bypass the five-attempt limit by obtaining a fresh session cookie and repeatedly re-authenticating to reset the counter, enabling unbounded TOTP code guessing.
CVE-2026-76213
Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-19. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 49(Track*)EG Risk 49/100SSVC: Track*
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 computedSeverity74% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle | Advisories | VulnCheck
https://www.vulncheck.com/advisories/phpmyfaq-before-2fa-brute-force-via-session-scoped-throttleAdmin 2FA brute-force throttle is session-scoped, so a fresh cookie jar resets the counter and TOTP codes can be guessed at will · Advisory · thorsten/phpMyFAQ · GitHub
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-f98m-hcjv-7rp9Vendor Advisories for CVE-2026-76213(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 11× in last 7d / 11× 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.
- 2026-08-21 01:13 UTCEG score recompute
- 2026-08-21 01:13 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:17 UTCGHSA enrichment
- 2026-08-20 03:21 UTCGHSA enrichment
- 2026-08-19 16:24 UTCEG score recompute
- 2026-08-19 16:24 UTCGHSA enrichment
- 2026-08-19 15:22 UTCEG score recompute
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76213?
When was CVE-2026-76213 disclosed?
Is CVE-2026-76213 actively exploited?
What is the CVSS score of CVE-2026-76213?
How do I remediate CVE-2026-76213?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76213
Is Your Infrastructure Affected by CVE-2026-76213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.