CVE-2026-46364
published 2026-05-15CVE-2026-46364: phpMyFAQ before 4.1.2 contains an unauthenticated SQL injection vulnerability in BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods…
PriorityP272critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EXPLOIT
EPSS
1.71%
74.5th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| thorsten | phpmyfaq | < 4.1.2 | 4.1.2 |
Detection & IOCsextracted from sources · hover to see the quote
sigma
detection:
selection:
User-Agent|contains: "8'"
status_code: 200
body|contains: 'Truncated incorrect DOUBLE'
condition: and- →Monitor HTTP requests to GET /api/captcha for User-Agent headers containing SQL injection payloads (e.g., single quotes, time-based blind SQLi patterns such as SLEEP() or boolean expressions). ↗
- →Alert on HTTP responses with status 200 that contain the MySQL error string 'Truncated incorrect DOUBLE' in the body, as this is a fingerprint of successful time-based blind SQL injection triggering against phpMyFAQ's captcha endpoint. ↗
- →The injection points are the BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods, which interpolate the User-Agent header directly into DELETE and INSERT SQL queries — focus WAF/IDS rules on the User-Agent field for requests to the captcha API. ↗
- →The attack is unauthenticated; no session or credentials are required. Prioritize detection at the perimeter/WAF layer for all requests to /api/captcha regardless of authentication state. ↗
- →Sensitive data at risk includes user credentials, admin tokens, and SMTP credentials — monitor for anomalous data exfiltration patterns in responses from the captcha endpoint. ↗
- ·Vulnerability affects phpMyFAQ versions before 4.1.2 only; instances already upgraded to 4.1.2 or later are not affected. ↗
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv4.09.3CRITICALCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
Nuclei
phpMyFAQ <= 4.1.1 - SQL Injection
nuclei·CVSS 9.8
CVE-2026-46364 [CRITICAL] phpMyFAQ <= 4.1.1 - SQL Injection
phpMyFAQ = 8'
- 'status_code == 200'
- 'contains(body, "Truncated incorrect DOUBLE")'
condition: and
# digest: 4a0a004730450221008fb66edd3f724b479351d4f1a5e386d34063722c76732c74a79468e0c9715a1e02202403723d77a3cf93cd499efdb84b441b50b41b6163f07dc17815057d66d3e0f7:922c64590222798bb761d5b6d8e72950
No writeups or analysis indexed.
2026-05-15
Published