phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authentication vulnerability that
Source GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 4.2.0-RC.2 or 4.1.12 when convenient.
Data as of 17 Nov 2026, 04:50 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 2.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.2 |
- Patch
- Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/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
If you cannot patch yet, organizations should protect session integrity to prevent hijacking and monitor for suspicious API calls related to WebAuthn passkey enrollment.
Description
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a missing authentication vulnerability. This flaw allows attackers with a hijacked session to enroll passkeys by exploiting the session and webauthn CSRF token. By calling specific API endpoints, attackers can replace the legitimate owner's passkeys, enabling persistent passwordless login that remains effective even after password changes or resets.
References
- github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j9ww-3xr9-wg48 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-130370 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/commit/f8d650590a2989763be87d7096bb942b72a725f6 (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-passkey-enrollment-missing-step-up-authentication (opens in a new tab)