CVE-2026-130362: thorsten phpMyFAQ · Observable Response Discrepancy
Affects thorsten phpMyFAQSource CVE Database V5
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, 02:06 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 thorsten 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
Upgrade phpMyFAQ to version 4.1.12 or later, or 4.2.0-RC.2 or later, where this vulnerability is fixed. Until patched, consider implementing additional rate limiting on the /api/webauthn/prepare endpoint and monitoring for suspicious login enumeration attempts.
Description
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contain an account enumeration vulnerability. This flaw allows unauthenticated attackers to identify valid usernames by observing differences in responses from the /api/webauthn/prepare endpoint. Attackers can reuse a single CSRF token without rate limiting to submit large username lists, facilitating discovery of administrator accounts for further attacks such as password spraying and phishing.
References
- github.com/thorsten/phpMyFAQ/security/advisories/GHSA-gm6r-r9vf-hmrf (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)