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.
Metrics
Affected Vendors & Products
References
History
Fri, 15 May 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 15 May 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thorsten
Thorsten phpmyfaq |
|
| Vendors & Products |
Thorsten
Thorsten phpmyfaq |
Fri, 15 May 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-05-15T21:12:54.058Z
Reserved: 2026-05-13T19:40:27.808Z
Link: CVE-2026-46359
Updated: 2026-05-15T21:12:45.597Z
Status : Received
Published: 2026-05-15T19:17:03.120
Modified: 2026-05-15T22:16:56.433
Link: CVE-2026-46359
No data.
OpenCVE Enrichment
Updated: 2026-05-15T20:45:08Z