CVE-2026-124432: thorsten phpMyFAQ · Observable Response Discrepancy
Affects thorsten phpMyFAQSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium · fixed in 4.1.11 : update thorsten phpMyFAQ when convenient.
Data as of 8 Nov 2026, 13:49 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.3 |
- Patch
- Available – fixed in 4.1.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected– | Fixed in– |
AI-suggested
The vulnerability is fixed in phpMyFAQ versions 4.1.11 and 4.2.0-beta.3 and later. Users should upgrade to these or newer versions to remediate the issue. No vendor advisory or patch links were provided, so confirm the fix by consulting official phpMyFAQ release notes or vendor advisories. Until patched, consider implementing rate limiting on the affected endpoint to reduce enumeration risk.
Description
phpMyFAQ versions 4.1.9 before 4.1.11 and 4.2.0 pre-releases before 4.2.0-beta.3 have an account enumeration vulnerability in the unauthenticated POST /api/webauthn/prepare-login endpoint. This endpoint returns stable credential IDs for passkey-registered accounts but a time-derived fallback ID for others, allowing attackers to distinguish existing accounts by comparing responses over time. The vulnerability has no rate limiting and can be exploited without authentication.