Strategic Overview
- Status
- Patched in 4.1.34
- Affected Core
- WordPress 5.8
- Affected Version
4.1 – < 5.8.3 · 18 branches- CVSS
- 7.4High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2022-21664
At a glance
CVE-2022-21664 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress 5.8 WordPress release line, affecting 4.1 – < 5.8.3 · 18 branches. It carries a CVSS score of 7.4 (reachable over the network; low attack complexity). The issue is fixed in version 4.1.34; sites on affected versions should update now. Disclosed January 2022, reported by Ben Bidner.
Vulnerability Overview
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to lack of proper sanitization in one of the classes, there's potential for unintended SQL queries to be executed. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 4.1.34. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WordPress 5.8 4.1 – < 5.8.3 · 18 branches takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WordPress 5.8 the fix is 4.1.34: builds 4.1 – < 5.8.3 · 18 branches are affected, anything from 4.1.34 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 4.1.34, 4.2.31, 4.3.27, 4.4.26, 4.5.25, 4.6.22, 4.7.22, 4.8.18, 4.9.19, 5.0.15, 5.1.12, 5.2.14, 5.3.11, 5.4.9, 5.5.8, 5.6.7, 5.7.5, 5.8.3
How does WordSec protect against this?
The attempt arrives as an ordinary request to WordPress 5.8: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 4.1.34 is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WordPress 5.8
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-4894: WordPress Core & WordPress MU < 1.2.5a - SQL Injection
CVE-2007-4894 - 9.8CVE-2007-1277: WordPress Core 2.2.1 Backdoor
CVE-2007-1277 - 9.8WordPress Core 2.1.1 Supply Chain Compromise
- 9.8CVE-2007-0107: WordPress Core <= 2.0.5 SQL Injection
CVE-2007-0107
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C