CVE-2025-57350 Vulnerability Analysis & Exploit Details

CVE-2025-57350
Vulnerability Scoring

8.6
/10
Severe Risk

Cybersecurity professionals consider CVE-2025-57350 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-57350 Details

Status: Analyzed

Last updated: 🕝 17 Oct 2025, 14:56 UTC
Originally published on: 🕕 24 Sep 2025, 18:15 UTC

Time between publication and last update: 22 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

CVE-2025-57350 Vulnerability Summary

CVE-2025-57350: 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.

Assessing the Risk of CVE-2025-57350

Access Complexity Graph

The exploitability of CVE-2025-57350 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-57350

With low attack complexity and no required privileges, CVE-2025-57350 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-57350, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-57350, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-57350 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2025-57350 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2025-57350 may slightly degrade system performance without fully affecting service availability.

CVE-2025-57350 References

External References

CWE Common Weakness Enumeration

CWE-1321

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:keyangxiang:csvtojson:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.16:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.16:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.18:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.18:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.19:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.19:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.20:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.20:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.3.21:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.3.21:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.4.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.4.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:0.5.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:0.5.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:1.1.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:1.1.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:keyangxiang:csvtojson:2.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:keyangxiang:csvtojson:2.0.8:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2025-57350: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-11940 – A security vulnerability has been detected in LibreWolf up to 143.0.4-1 on Windows. This affects an unknown function of the file assets/setup.nsi o...
  • CVE-2025-11939 – A vulnerability was determined in ChurchCRM up to 5.18.0. This issue affects some unknown processing of the file src/ChurchCRM/Backup/RestoreJob.ph...
  • CVE-2025-11938 – A vulnerability was found in ChurchCRM up to 5.18.0. This vulnerability affects unknown code of the file setup/routes/setup.php. Performing manipul...
  • CVE-2025-62672 – rplay through 3.3.2 allows attackers to cause a denial of service (SIGSEGV and daemon crash) or possibly have unspecified other impact. This occurs...
  • CVE-2025-47410 – Apache Geode is vulnerable to CSRF attacks through GET requests to the Management and Monitoring REST API that could allow an attacker who has tric...