PatchTheCVECVE-2022-4368: The WP CSV WordPress plugin through 1.8.0.0 does not sanitize and escape a parameter before outputting it back
CVE-2022-4368 is a medium-severity flaw (CVSS 6.1) affecting wp csv. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP CSV WordPress plugin through 1.8.0.0 does not sanitize and escape a parameter before outputting it back in the page when importing a CSV, and doe snot have CSRF checks in place as well, leading to a Reflected Cross-Site Scripting.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 83%) |
| CISA exploited list | No |
| Published | 2023-01-09 |
| 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-4368?
wp csv: upgrade to newer than 1.8.0.0. Exact commands for each OS are on this page.
Is CVE-2022-4368 being exploited?
CVE-2022-4368 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-4368 affect?
CVE-2022-4368 affects wp csv. Severity is medium (CVSS 6.1). The WP CSV WordPress plugin through 1.8.0.0 does not sanitize and escape a parameter before outputting it back in the page when importing a CSV, and doe snot have CSRF checks in place as well, leading to a Reflected Cross-Site Scripting.
How urgent is CVE-2022-4368?
Priority 31/100. Public exploit reference