Authenticated SQL injection via unescaped OAuth claims
Published May 15, 2026 · Updated May 15, 2026
SQL injection in CurrentUser::setTokenData in phpMyFAQ before 4.1.2 allows remote authenticated users to execute arbitrary SQL. The method formats refresh tokens, access tokens, code verifiers, and JSON-encoded JWT data directly into an SQL UPDATE without database escaping. Exploitation requires Azure AD authentication and an attacker-controlled account claim containing SQL metacharacters; successful injection permits reading, changing, or deleting database content.
Summary
What happened
SQL injection in CurrentUser::setTokenData in phpMyFAQ before 4.1.2 allows remote authenticated users to execute arbitrary SQL. The method formats refresh tokens, access tokens, code verifiers, and JSON-encoded JWT data directly into an SQL UPDATE without database escaping. Exploitation requires Azure AD authentication and an attacker-controlled account claim containing SQL metacharacters; successful injection permits reading, changing, or deleting database content.
The record
- CVE
- CVE-2026-46359
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Azure AD crafted-claim SQL injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo