# CVE-2022-4368: WP CSV <= 1.8.0.0 - Reflected XSS via CSV Import

> Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the WP CSV plugin's import feature, potentially leading to session hijacking.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-42p3-xp7q-pwv6

## What is CVE-2022-4368?

CVE-2022-4368 is a medium-severity cross-site scripting vulnerability in Unknown WP CSV, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by CVE-2022-4368?

It affects 1 product.


Products: Cpkwebsolutions Wp Csv.

## How do I fix CVE-2022-4368?

No fix has been published for CVE-2022-4368 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4368 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4368 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4368 and fix it if it is affected.

What it is: CVE-2022-4368 is a medium-severity cross-site scripting vulnerability in Unknown WP CSV, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4368 exists.

Affected product: Unknown WP CSV. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4368/ (Markdown: https://insights.sbomify.com/CVE-2022-4368/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4368
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4368
- OSV: https://osv.dev/vulnerability/CVE-2022-4368

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4368/
Summaries are generated and may contain mistakes; the official description above is the record.