phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an account enumeration vulnerability that
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.2.0-RC.2 or 4.1.12 when convenient.
Data as of 17 Nov 2026, 04:51 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 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 16 Nov 2026.
What to do
Upgrade phpMyFAQ to 4.2.0-RC.2 or 4.1.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
| thorstenphpMyFAQ | Affected
| Fixed in
|
PackagistphpMyFAQpkg:composer/phpMyFAQOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in phpMyFAQ versions 4.1.12 and 4.2.0-RC.2 and later. Users should upgrade to these or newer versions to remediate the issue. No vendor advisory or patch links were provided, so confirm patch availability from official phpMyFAQ sources before applying updates. Until patched, consider implementing rate limiting on the affected endpoint and monitoring for suspicious activity.
Description
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an account enumeration vulnerability. This flaw allows unauthenticated attackers to distinguish valid usernames by analyzing different responses from the POST /api/webauthn/prepare endpoint. Attackers can exploit this by submitting username wordlists using a single CSRF token without rate limiting, enabling discovery of administrator accounts for further attacks such as password spraying or phishing.
References
- github.com/thorsten/phpMyFAQ/security/advisories/GHSA-gm6r-r9vf-hmrf (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-130362 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/commit/6ec52d1e914bc88f48f4b47e441a078f995f58ea (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.1.12 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2 (opens in a new tab)
- vulncheck.com/advisories/phpmyfaq-4.1.9-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-account-enumeration-via-webauthn-prepare (opens in a new tab)