# CVE-2026-76214: phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge

> Attackers can replay captured WebAuthn assertions to bypass authentication and take over user accounts in phpMyFAQ.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-f534-wv9g-wx2w, GHSA-wg4g-rgc9-r6gj

## What is CVE-2026-76214?

CVE-2026-76214 is a critical authentication bypass vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

phpMyFAQ before 4.1.7 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.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-76214?

It affects 1 product.


Products: Phpmyfaq Phpmyfaq.

## How do I fix CVE-2026-76214?

No fix has been published for CVE-2026-76214 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76214 being exploited?

There is no known exploitation of CVE-2026-76214 in the wild and no public exploit code.

## Other vulnerabilities in Phpmyfaq Phpmyfaq

- [CVE-2023-0310](https://insights.sbomify.com/CVE-2023-0310/): Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq (critical 9.8)
- [CVE-2022-4407](https://insights.sbomify.com/CVE-2022-4407/): Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq (critical 9.8)
- [CVE-2017-11187](https://insights.sbomify.com/CVE-2017-11187/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-76213](https://insights.sbomify.com/CVE-2026-76213/): phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle (critical 9.1)
- [CVE-2023-5316](https://insights.sbomify.com/CVE-2023-5316/): Cross-site Scripting (XSS) - DOM in thorsten/phpmyfaq (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76214 and fix it if it is affected.

What it is: CVE-2026-76214 is a critical authentication bypass vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76214 in the wild and no public exploit code.

Affected product: Phpmyfaq Phpmyfaq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76214/ (Markdown: https://insights.sbomify.com/CVE-2026-76214/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76214
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76214
- OSV: https://osv.dev/vulnerability/CVE-2026-76214

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76214/
Summaries are generated and may contain mistakes; the official description above is the record.