CVE-2026-46364: thorsten phpmyfaq · SQL Injection
Affects thorsten phpmyfaqSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical : upgrade to 4.1.2 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 3.1 | 9.8 |
|---|---|---|
| CNA (VulnCheck) | CVSS 4.0 | 9.3 |
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: evidence found.
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 and thorsten/phpMyFAQ to 4.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpmyfaq | Affected
| Fixed in
|
GitHubthorsten/phpMyFAQpkg:github/thorsten/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, users should consider restricting access to the /api/captcha endpoint or implementing web application firewall (WAF) rules to block malicious User-Agent headers targeting this endpoint. Monitoring for unusual traffic patterns to this API may also help detect exploitation attempts. Avoid exposing vulnerable versions of phpMyFAQ to untrusted networks.
Description
phpMyFAQ before 4.1.2 contains an unauthenticated SQL injection vulnerability in BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods that interpolate unsanitized User-Agent headers into DELETE and INSERT queries. Unauthenticated attackers can exploit the public GET /api/captcha endpoint by crafting malicious User-Agent headers to perform time-based blind SQL injection, extracting sensitive data including user credentials, admin tokens, and SMTP credentials from the database.