PatchTheCVECVE-2022-1578: The My wpdb WordPress plugin before 2.5 is missing CSRF check when running SQL queries, which could allow atta
CVE-2022-1578 is a high-severity flaw (CVSS 8.8) affecting my wpdb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The My wpdb WordPress plugin before 2.5 is missing CSRF check when running SQL queries, which could allow attacker to make a logged in admin run arbitrary SQL query via a CSRF attack
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 60%) |
| CISA exploited list | No |
| Published | 2022-11-21 |
| 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-1578?
my wpdb: upgrade to 2.5. Exact commands for each OS are on this page.
Is CVE-2022-1578 being exploited?
CVE-2022-1578 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-1578 affect?
CVE-2022-1578 affects my wpdb. Severity is high (CVSS 8.8). The My wpdb WordPress plugin before 2.5 is missing CSRF check when running SQL queries, which could allow attacker to make a logged in admin run arbitrary SQL query via a CSRF attack
How urgent is CVE-2022-1578?
Priority 46/100. High severity; Public exploit reference