CVE-2022-3249: The WP CSV Exporter WordPress plugin before 1.3.7 does not properly sanitise and escape some parameters before
CVE-2022-3249 is a high-severity flaw (CVSS 7.2) affecting wp csv exporter. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP CSV Exporter WordPress plugin before 1.3.7 does not properly sanitise and escape some parameters before using them in a SQL statement, allowing high privilege users such as admin to perform SQL injection attacks
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.0% (top 36%) |
| CISA exploited list | No |
| Published | 2022-12-05 |
| 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-3249?
wp csv exporter: upgrade to 1.3.7. Exact commands for each OS are on this page.
Is CVE-2022-3249 being exploited?
CVE-2022-3249 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-3249 affect?
CVE-2022-3249 affects wp csv exporter. Severity is high (CVSS 7.2). The WP CSV Exporter WordPress plugin before 1.3.7 does not properly sanitise and escape some parameters before using them in a SQL statement, allowing high privilege users such as admin to perform SQL injection attacks
How urgent is CVE-2022-3249?
Priority 46/100. High severity; Public exploit reference
Software pages
Related CVEs
- CVE-2022-3605 HIGH 7.8 UPGRADE The WP CSV Exporter WordPress plugin before 1.3.7 does not properly escape the fields when exporting data as C