CVE-2021-24629: The Post Content XMLRPC WordPress plugin through 1.0 does not sanitise or escape multiple GET/POST parameters
CVE-2021-24629 is a high-severity flaw (CVSS 7.2) affecting post content xmlrpc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Post Content XMLRPC WordPress plugin through 1.0 does not sanitise or escape multiple GET/POST parameters before using them in SQL statements in the admin dashboard, leading to an authenticated SQL Injections
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.2 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | None |
| EPSS exploit chance | 1.5% (top 25%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2021-11-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2021-24629?
post content xmlrpc: upgrade to newer than 1.0. Exact commands for each OS are on this page.
Is CVE-2021-24629 being exploited?
CVE-2021-24629 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2021-24629 affect?
CVE-2021-24629 affects post content xmlrpc. Severity is high (CVSS 7.2). The Post Content XMLRPC WordPress plugin through 1.0 does not sanitise or escape multiple GET/POST parameters before using them in SQL statements in the admin dashboard, leading to an authenticated SQL Injections
How urgent is CVE-2021-24629?
Priority 49/100. High severity; Public exploit reference