CVE-2026-46364: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in thorsten phpmyfaq
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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-46364) affects phpMyFAQ before version 4.1.2 and involves improper neutralization of special elements in SQL commands, specifically in the BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods. Unsanitized User-Agent headers are directly interpolated into SQL DELETE and INSERT queries, allowing unauthenticated attackers to exploit the GET /api/captcha endpoint via time-based blind SQL injection. Successful exploitation can lead to extraction of sensitive database information including user credentials, administrative tokens, and SMTP credentials. The vulnerability is rated critical with a CVSS 3.1 score of 9.8, reflecting its high impact on confidentiality, integrity, and availability. No patch or official fix has been confirmed as of the published date.
Potential Impact
An unauthenticated attacker can exploit this SQL injection vulnerability to perform time-based blind SQL injection attacks against the phpMyFAQ database. This can result in unauthorized disclosure of sensitive information such as user credentials, admin tokens, and SMTP credentials. The vulnerability affects confidentiality, integrity, and availability of the application and its data, making it critical. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider restricting access to the vulnerable endpoint or implementing web application firewall (WAF) rules to detect and block suspicious User-Agent header patterns targeting the /api/captcha endpoint. Avoid exposing the vulnerable phpMyFAQ versions to untrusted networks.
CVE-2026-46364: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in thorsten phpmyfaq
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-46364) affects phpMyFAQ before version 4.1.2 and involves improper neutralization of special elements in SQL commands, specifically in the BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods. Unsanitized User-Agent headers are directly interpolated into SQL DELETE and INSERT queries, allowing unauthenticated attackers to exploit the GET /api/captcha endpoint via time-based blind SQL injection. Successful exploitation can lead to extraction of sensitive database information including user credentials, administrative tokens, and SMTP credentials. The vulnerability is rated critical with a CVSS 3.1 score of 9.8, reflecting its high impact on confidentiality, integrity, and availability. No patch or official fix has been confirmed as of the published date.
Potential Impact
An unauthenticated attacker can exploit this SQL injection vulnerability to perform time-based blind SQL injection attacks against the phpMyFAQ database. This can result in unauthorized disclosure of sensitive information such as user credentials, admin tokens, and SMTP credentials. The vulnerability affects confidentiality, integrity, and availability of the application and its data, making it critical. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider restricting access to the vulnerable endpoint or implementing web application firewall (WAF) rules to detect and block suspicious User-Agent header patterns targeting the /api/captcha endpoint. Avoid exposing the vulnerable phpMyFAQ versions to untrusted networks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-05-13T19:40:27.809Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a076ec4ec166c07b0830ab6
Added to database: 5/15/2026, 7:06:44 PM
Last enriched: 5/15/2026, 7:22:05 PM
Last updated: 5/16/2026, 4:25:13 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.