phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields
thorsten phpmyfaq
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| thorsten/phpmyfaq Packagist |
|
|
| phpmyfaq/phpmyfaq Packagist |
|
|
thorsten phpmyfaq
| Product | Affected | Fixed in |
|---|---|---|
| thorsten/phpmyfaq Packagist |
|
|
| phpmyfaq/phpmyfaq Packagist |
|
|
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.
From the CVE record · VulnCheck
phpMyFAQ before 4.1.2 has a SQL injection vulnerability in CurrentUser::setTokenData. An authenticated attacker with an Azure AD account containing SQL metacharacters in its display name or JWT claims can inject malicious OAuth token claims and execute arbitrary database queries.
Anyone running phpMyFAQ before 4.1.2 through the thorsten/phpmyfaq or phpmyfaq/phpmyfaq Packagist package should check their installation.