CVE-2022-0771: The SiteSuperCharger WordPress plugin before 5.2.0 does not validate, sanitise and escape various user inputs
CVE-2022-0771 is a critical-severity flaw (CVSS 9.8) affecting sitesupercharger. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The SiteSuperCharger WordPress plugin before 5.2.0 does not validate, sanitise and escape various user inputs before using them in SQL statements via AJAX actions (available to both unauthenticated and authenticated users), leading to Unauthenticated SQL Injections
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.6% (top 24%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2022-05-02 |
| 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-2022-0771?
sitesupercharger: upgrade to 5.2.0. Exact commands for each OS are on this page.
Is CVE-2022-0771 being exploited?
CVE-2022-0771 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-2022-0771 affect?
CVE-2022-0771 affects sitesupercharger. Severity is critical (CVSS 9.8). The SiteSuperCharger WordPress plugin before 5.2.0 does not validate, sanitise and escape various user inputs before using them in SQL statements via AJAX actions (available to both unauthenticated and authenticated users), leading to Unaut
How urgent is CVE-2022-0771?
Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action