# CVE-2025-57350: CSVTOJSON has a prototype pollution vulnerability

> Prototype pollution in csvtojson allows attackers to cause denial of service or unexpected behavior via malicious CSV headers.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** CLEANSTART-2026-MC89115, CLSA-2026-1780620677, GHSA-vrw9-g62v-7fmf

## What is CVE-2025-57350?

CVE-2025-57350 is a high-severity vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The csvtojson package, a tool for converting CSV data to JSON with customizable parsing capabilities, contains a prototype pollution vulnerability in versions prior to 2.0.10. This issue arises due to insufficient sanitization of nested header names during the parsing process in the parser_jsonarray component. When processing CSV input containing specially crafted header fields that reference prototype chains (e.g., using __proto__ syntax), the application may unintentionally modify properties of the base Object prototype. This vulnerability can lead to denial of service conditions or unexpected behavior in applications relying on unmodified prototype chains, particularly when untrusted CSV data is processed. The flaw does not require user interaction beyond providing a maliciously constructed CSV file.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-57350?

2 open source packages ship an affected version, including csvtojson. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `csvtojson` | npm | All versions | 2.0.13 |
| `csvtojson` | npm | All versions | 2.0.13 |

Products: Keyangxiang Csvtojson.

## How do I fix CVE-2025-57350?

Upgrade csvtojson to 2.0.13 or later.

## Is CVE-2025-57350 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57350 and fix it if it is affected.

What it is: CVE-2025-57350 is a high-severity vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57350 exists.

Affected packages and fixed versions:
- csvtojson (npm): affected all versions; fixed in 2.0.13
- csvtojson (npm): affected all versions; fixed in 2.0.13

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-2025-57350/ (Markdown: https://insights.sbomify.com/CVE-2025-57350/index.md)
```

## Sources

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

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