LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7795: Command Injection

The package get-npm-package-version before 1.0.7 are vulnerable to Command Injection via main function in index.js.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-7795 affects the npm package get-npm-package-version before 1.0.7. The reported issue is command injection through its main function, meaning attacker-controlled input could cause unintended commands to run where the package is used. Business urgency depends on whether this package is present and reachable from untrusted input.

Executive priority

Prioritize remediation if the package appears in production, CI/CD, or internet-facing workflows. The package is small, so upgrading or removing it should usually be low effort compared with the risk of command execution.

Technical view

The source bundle identifies get-npm-package-version versions before 1.0.7 as vulnerable to command injection in index.js. CVSS 3.1 is 7.3 high with network attack vector, low complexity, no privileges, and no user interaction. The bundle names a fixing commit and version boundary, but does not provide operational exploit detail.

Likely exposure

Exposure is most likely in Node.js applications, build tools, or automation that directly or transitively depend on get-npm-package-version before 1.0.7 and pass untrusted input into the package.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source in the bundle establishes active exploitation in the wild. Treat exploitability as plausible based on the command injection classification and CVSS metadata, but verify local reachability.

Researcher notes

Evidence is limited to package-level advisory metadata, npm package reference, vulnerable source reference, and a fixing commit. Validate reachability before escalating severity beyond high. Do not assume active exploitation without additional threat intelligence.

Mitigation direction

  • Upgrade get-npm-package-version to 1.0.7 or later.
  • Regenerate lockfiles so vulnerable transitive versions are removed.
  • Remove the package if it is no longer needed.
  • Do not pass untrusted input into affected package code paths.
  • Check upstream vendor guidance if upgrade constraints exist.

Validation and detection

  • Search package.json and lockfiles for get-npm-package-version below 1.0.7.
  • Check SBOM or dependency scanner output for CVE-2020-7795.
  • Confirm production build artifacts use the patched dependency version.
  • Identify application paths that call the package main function.
  • Review whether any caller accepts external or user-controlled input.
Prepared
Confidence
high
Sources
6

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-7795 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2020-7795Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aget-npm-package-versionunspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.