# CVE-2022-21241: Cross-site scripting in CSV+

> Remote attackers can inject scripts or OS commands via crafted CSV files in the CSV+ library, potentially leading to code execution.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 8 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h95w-c385-8x7j

## What is CVE-2022-21241?

CVE-2022-21241 is a critical cross-site scripting vulnerability in Plus one CSV+, published on 8 Feb 2022. 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

Cross-site scripting vulnerability in CSV+ prior to 0.8.1 allows a remote unauthenticated attacker to inject an arbitrary script or an arbitrary OS command via a specially crafted CSV file that contains HTML a tag.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Csv\+ Project Csv\+.

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

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

## Is CVE-2022-21241 being exploited?

There is no known exploitation of CVE-2022-21241 in the wild and no public exploit code.

Public exploit code:

- 👻 [PoC] CSV+ 0.8.0 - Arbitrary Code Execution (CVE-2022-21241) (github_poc): https://github.com/nanaao/csv-plus_vulnerability

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21241 is a critical cross-site scripting vulnerability in Plus one CSV+, published on 8 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-21241 in the wild and no public exploit code.

Affected product: Plus one 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-21241/ (Markdown: https://insights.sbomify.com/CVE-2022-21241/index.md)
```

## Sources

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

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