CVE-2025-12613: Versions of the package cloudinary before 2.7.0 are vulnerable to Arbitrary Argument Injection due to impro...
Versions of the package cloudinary before 2.7.0 are vulnerable to Arbitrary Argument Injection due to improper parsing of parameter values containing an ampersand. An attacker can inject additional, unintended parameters. This could lead to a variety of malicious outcomes, such as bypassing security checks, altering data, or manipulating the application's behavior.
**Note:**
Following our established security policy, we attempted to contact the maintainer regarding this vulnerability, but haven't received a response.
Security readout for executives and security teams
Plain-English summary
CVE-2025-12613 affects the npm cloudinary package before 2.7.0. Improper parsing of ampersands in parameter values can let an unauthenticated attacker add unintended parameters. Business risk depends on how an application uses Cloudinary transformations, uploads, or signed parameters, but the reported impact includes bypassing checks or changing application behavior.
Executive priority
Prioritize remediation for internet-facing services or workflows that let users influence Cloudinary parameters. Treat as high priority because exploitation requires no privileges or user interaction, but validate actual business exposure before emergency response.
Technical view
The issue is classified as CWE-88, arbitrary argument injection. Parameter values containing an ampersand may be parsed as additional arguments by cloudinary versions before 2.7.0. The CVSS 4.0 score is 8.8, network exploitable, low complexity, no privileges, and no user interaction required. Public references include Snyk, a GitHub pull request, and a related commit.
Likely exposure
Applications using the npm cloudinary package before 2.7.0 are potentially exposed, especially where user-controlled input reaches Cloudinary parameter construction. Exposure is lower where inputs are strictly controlled or not used in vulnerable parameter paths.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue is remotely reachable in the CVSS assessment and could affect integrity by injecting unintended parameters, but public sources here do not prove real-world attacks.
Researcher notes
Evidence is limited to the CVE record, Snyk advisory, and GitHub change references. The advisory states maintainer contact did not receive a response. Do not assume broader Cloudinary platform exposure; the identified affected component is the npm cloudinary package before 2.7.0.
Mitigation direction
Inventory applications using the npm cloudinary package.
Upgrade cloudinary to 2.7.0 or later where compatible.
Review vendor, Snyk, and GitHub guidance for final fix status.
Restrict user-controlled values used in Cloudinary parameters.
Add input validation around parameters containing ampersands.
Validation and detection
Check package manifests and lockfiles for cloudinary versions below 2.7.0.
Confirm deployed containers or builds include the upgraded dependency.
Review code paths passing user input into Cloudinary parameters.
Test application behavior for rejected or safely encoded ampersand values.
Monitor dependency scanners for CVE-2025-12613 findings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.