CVE-2026-130354: thorsten phpMyFAQ · Authentication Bypass Using an Alternate Path or Channel
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. No other mitigation or temporary workaround is indicated by the vendor advisory.
Description
phpMyFAQ versions 4.1.0 up to but not including 4.1.12, and 4.2.0-alpha up to but not including 4.2.0-RC.2, contain an authentication bypass vulnerability in the POST /api/webauthn/prepare endpoint. This flaw allows anonymous attackers to create accounts that are automatically active, bypassing manual activation and domain whitelisting. Attackers can obtain a CSRF token without authentication and register accounts with unverified emails, gaining access to content and functions restricted to registered users.
References
- github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8mmg-4qpv-p7x5 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/commit/a707f76b3db760f15a15ca0860ea36e30ab1deea (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.0-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-authentication-bypass-via-webauthn-prepare (opens in a new tab)