dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-63706

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NPM package next-npm-version1.0.1 is vulnerable to Command injection.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The NPM package next-npm-version version 1.0.1 contains a command injection vulnerability allowing attackers to execute arbitrary system commands through unsanitized input, likely due to unsafe use of exec, spawn, or similar functions that pass user-controlled data to the operating system shell.

MitigationUpgrade to a patched version if available, otherwise audit and sanitize all input passed to system command functions or replace command execution with safer alternatives; remove the package if unused.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify next-npm-version is in dependencies
    Inspect your package.json file (both dependencies and devDependencies sections) and run 'npm list next-npm-version' to confirm the package is installed
    Affected if The package appears in your project dependencies
  2. Check installed version
    Run 'npm list next-npm-version' or check package-lock.json to determine the exact version number installed
    Affected if Version is 1.0.1
  3. Inspect source code for unsafe exec usage
    Locate the package in node_modules/next-npm-version and examine the JavaScript source files for uses of exec(), execSync(), spawn(), spawnSync(), or similar functions that pass variables to shell commands without sanitization
    Affected if Code contains unsanitized command execution functions receiving external input
  4. Determine if package processes external input
    Review your codebase for places where next-npm-version is imported and used. Check if any user-controlled data (request parameters, config values, environment variables) flows to functions exported by this package
    Affected if External or user-controlled input can reach the package's command execution logic
  5. Audit package usage in running application
    Search your codebase for require('next-npm-version') or import statements loading this package, and trace data flow from HTTP inputs or external sources to these calls
    Affected if The package is actively imported and receives input that could reach the vulnerable functions

You are affected if next-npm-version version 1.0.1 is installed AND your application passes any external or user-controlled input to functions provided by this package.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version if available, otherwise audit and sanitize all input passed to system command functions or replace command execution with safer alternatives; remove the package if unused.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-63706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-63706 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data