# CVE-2026-124432: phpMyFAQ before 4.1.11 and 4.2.0-beta.3 Account Enumeration via WebAuthn prepare-login


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-2rvx-pqfw-q35r, GHSA-f46v-r9r2-mgmc

## What is CVE-2026-124432?

CVE-2026-124432 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 8 Nov 2026. 

### Official description

phpMyFAQ 4.1.9 before 4.1.11 and 4.2.0 pre-releases before 4.2.0-beta.3 contain an account enumeration vulnerability in the unauthenticated POST /api/webauthn/prepare-login endpoint, which returns stable stored credential IDs for passkey-registered accounts but an md5(time())-derived fallback ID otherwise. Unauthenticated attackers can compare allowCredentials IDs from requests sent more than one second apart, without rate limiting, to identify existing passkey-registered accounts and their credential IDs.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2026-124432 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124432 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124432 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124432 exists.

Affected product: thorsten 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-124432/ (Markdown: https://insights.sbomify.com/CVE-2026-124432/index.md)
```

## Sources

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

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