What is CVE-2025-57350?

CVE-2025-57350 is a medium-severity security vulnerability in csvtojson (npm), affecting versions < 2.0.13. It is fixed in 2.0.13.

Which versions of csvtojson are affected by CVE-2025-57350?

csvtojson (npm) versions < 2.0.13 is affected.

Is there a fix for CVE-2025-57350?

Yes. CVE-2025-57350 is fixed in 2.0.13. Upgrade to this version or later.

Is CVE-2025-57350 exploitable, and should I be worried?

Whether CVE-2025-57350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-57350 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-57350 in csvtojson

Q: Which versions of csvtojson are affected by CVE-2025-57350?

csvtojson (npm) versions < 2.0.13 is affected.

Q: Is there a fix for CVE-2025-57350?

Yes. CVE-2025-57350 is fixed in 2.0.13. Upgrade to this version or later.

Q: Is CVE-2025-57350 exploitable, and should I be worried?

Whether CVE-2025-57350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-57350 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-57350?

Upgrade csvtojson to 2.0.13 or later.

Summary

CSVTOJSON has a prototype pollution vulnerability

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.

Impact

Affected versions

csvtojson (< 2.0.13)

Security releases

csvtojson → 2.0.13 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade csvtojson to 2.0.13 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-57350? CVE-2025-57350 is a medium-severity security vulnerability in csvtojson (npm), affecting versions < 2.0.13. It is fixed in 2.0.13.
Which versions of csvtojson are affected by CVE-2025-57350? csvtojson (npm) versions < 2.0.13 is affected.
Is there a fix for CVE-2025-57350? Yes. CVE-2025-57350 is fixed in 2.0.13. Upgrade to this version or later.
Is CVE-2025-57350 exploitable, and should I be worried? Whether CVE-2025-57350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-57350 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-57350? Upgrade csvtojson to 2.0.13 or later.