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.
Problem types
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Product status
Any version before 4.1.2
4.1.2 (semver)
Credits
adrgs
aisafe-bot
References
github.com/...pMyFAQ/security/advisories/GHSA-pm8c-3qq3-72w7
github.com/...pMyFAQ/security/advisories/GHSA-pm8c-3qq3-72w7 (GHSA Advisory GHSA-pm8c-3qq3-72w7)
www.vulncheck.com/...endata-via-unescaped-oauth-token-fields (VulnCheck Advisory: phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields)