phpMyFAQ before 4.1.7 (affected versions <= 4.1.5) fails to persist the WebAuthn login challenge generated by prepareForLogin, because neither WebAuthn controller saves the mutated key objects back to the database. At login the anti-replay comparison is skipped by its own null guard, allowing an attacker who captures a successful WebAuthn assertion to replay it indefinitely and authenticate as the user without any interaction or hardware key.
CVE-2026-76214
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
- 33(Track)EG Risk 33/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%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge | Advisories | VulnCheck
https://www.vulncheck.com/advisories/phpmyfaq-before-webauthn-replay-attack-via-challengeWebAuthn login challenge is never persisted, so the replay guard is skipped and captured assertions can be replayed · Advisory · thorsten/phpMyFAQ · GitHub
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-f534-wv9g-wx2wVendor Advisories for CVE-2026-76214(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 13× in last 7d / 13× 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 04:12 UTCEG score recompute
- 2026-08-21 04:12 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:38 UTCEG score recompute
- 2026-08-20 16:38 UTCGHSA enrichment
- 2026-08-20 15:45 UTCEG score recompute
- 2026-08-20 15:45 UTCGHSA enrichment
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-20 02:01 UTCEG score recompute
- 2026-08-20 02:01 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-294
- CVE-2021-22640NVD 7.5EG 9.8CRITICAL
- CVE-2022-29334EG 9.8CRITICAL
- CVE-2022-22806EG 9.8EPSS p96CRITICAL
- CVE-2020-35551EG 9.8CRITICAL
- CVE-2018-19025EG 9.8CRITICAL
- CVE-2018-17932EG 9.8CRITICAL
- CVE-2019-18226EG 9.8CRITICAL
- CVE-2018-7790EG 9.8CRITICAL
- CVE-2017-3191EG 9.8EPSS p99CRITICAL
- CVE-2017-6034EG 9.8EPSS p92CRITICAL
Frequently asked(5)
What is CVE-2026-76214?
When was CVE-2026-76214 disclosed?
Is CVE-2026-76214 actively exploited?
What is the CVSS score of CVE-2026-76214?
How do I remediate CVE-2026-76214?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76214
Is Your Infrastructure Affected by CVE-2026-76214?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.