CVE-2026-46359 phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields
Authenticated attackers can execute arbitrary SQL queries by injecting malicious OAuth token claims into phpMyFAQ, potentially compromising database integrity.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-46359?
CVE-2026-46359 is a high-severity SQL injection vulnerability in thorsten phpmyfaq, published on 15 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
phpMyFAQ before 4.1.2 contains a sql injection vulnerability in CurrentUser::setTokenData that allows authenticated attackers to execute arbitrary SQL by injecting malicious OAuth token claims. Attackers with Azure AD accounts containing SQL metacharacters in display names or JWT claims can break out of string literals and execute arbitrary database queries.
Weakness: CWE-89
Which versions are affected by CVE-2026-46359?
4 open source packages ship an affected version, including thorsten/phpmyfaq and phpmyfaq/phpmyfaq.
| Package | Affected | Fixed in |
|---|---|---|
thorsten/phpmyfaq Packagist | All versions | 4.1.2 |
thorsten/phpmyfaq Packagist | All versions | 4.1.2 |
phpmyfaq/phpmyfaq Packagist | All versions | 4.1.2 |
phpmyfaq/phpmyfaq Packagist | All versions | 4.1.2 |
How do I fix CVE-2026-46359?
Upgrade thorsten/phpmyfaq to 4.1.2 or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-46359 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46359 exists.
Sources
Also known as GHSA-pm8c-3qq3-72w7.