Is CVE-2026-124432 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-124432 being exploited in the wild.

How severe is CVE-2026-124432?

High severity, with a CVSS score of 7.3, published 8 November 2026.

Which products and versions are affected?

Thorsten phpMyFAQ 4.1.9 before 4.1.11 and 4.2.0-beta.0 through 4.2.0-beta.2.

Is there a fix for CVE-2026-124432?

Yes: fixed in phpMyFAQ 4.1.11, 4.2.0-beta.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-124432 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-124432?

Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-124432: phpMyFAQ WebAuthn account enumeration in prepare-login

CVE-2026-124432 · Severity: high · CVSS 7.3 · Published 2026-11-08

phpMyFAQ is a frequently-asked-questions knowledge base system used to provide customer support. An unauthenticated attacker can enumerate which user accounts have WebAuthn passkeys registered by comparing responses from the login preparation endpoint sent more than one second apart. This allows reconnaissance of valid accounts and their authentication configuration, which can enable targeted phishing or credential-stuffing attacks. Additionally, attackers can disrupt passkey authentication for targeted accounts without rate limiting.

Technologies: Thorsten phpMyFAQ. Vendors: Thorsten.

Quick answers

Is CVE-2026-124432 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-124432 being exploited in the wild.
How severe is CVE-2026-124432?: High severity, with a CVSS score of 7.3, published 8 November 2026.
Which products and versions are affected?: Thorsten phpMyFAQ 4.1.9 before 4.1.11 and 4.2.0-beta.0 through 4.2.0-beta.2.
Is there a fix for CVE-2026-124432?: Yes: fixed in phpMyFAQ 4.1.11, 4.2.0-beta.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-124432 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-124432?: Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: phpMyFAQ 4.1.11, 4.2.0-beta.3

Technical details

The POST /api/webauthn/prepare-login endpoint exhibits an observable response discrepancy: requests for passkey-registered accounts return stable stored credential IDs, while requests for non-existing or passkey-less accounts return a pseudo-random ID derived from md5(time()) that changes every second. An unauthenticated attacker can compare allowCredentials arrays from requests spaced more than one second apart to distinguish passkey-registered accounts from others, and the endpoint is not rate-limited and bypasses CSRF checks. The endpoint also stamps fresh login challenges onto target accounts' passkey records with each request, enabling denial-of-service of passkey authentication.

Affected products

thorsten phpMyFAQ 4.1.9 before 4.1.11 and 4.2.0-beta.0 through 4.2.0-beta.2

Timeline

2026-10-23: disclosed
2026-11-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.