How severe is GHSA-qjg4-w4c6-f6c6?

GHSA-qjg4-w4c6-f6c6 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qjg4-w4c6-f6c6?

GHSA-qjg4-w4c6-f6c6 affects the following packages: mversion (npm). Ecosystems affected: npm.

How do I fix GHSA-qjg4-w4c6-f6c6?

Update mversion to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjg4-w4c6-f6c6 is resolved across your whole dependency graph.

How do I detect GHSA-qjg4-w4c6-f6c6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mversion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qjg4-w4c6-f6c6 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-qjg4-w4c6-f6c6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qjg4-w4c6-f6c6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qjg4-w4c6-f6c6?

GHSA-qjg4-w4c6-f6c6 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qjg4-w4c6-f6c6?

GHSA-qjg4-w4c6-f6c6 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qjg4-w4c6-f6c6 published, and has it been updated?

GHSA-qjg4-w4c6-f6c6 was published on June 18, 2020 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

Command injection in mversionGHSA-qjg4-w4c6-f6c6

HIGHFix: mikaelbr/mversion@6c76c9e

GHSA-qjg4-w4c6-f6c6 is a high-severity (CVSS 7.3) CWE-77 vulnerability in mversion. A fix is available for mversion — see the affected versions and patch details below.

Also known asCVE-2020-4059

Published

Jun 18, 2020

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-qjg4-w4c6-f6c6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

10other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mversionnpm

4Kdownloads / week

Description

In mversion before 2.0.0, there is a command injection vulnerability. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This vulnerability is patched by version 2.0.0. Previous releases are deprecated in npm. As a workaround, make sure to escape git commit messages when using the commitMessage option for the update function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mversion`	all versions	2.0.0`npm install mversion@2.0.0`

Affected Products

1 product · 1 configurations

Application

mversionmversion_project

< 2.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mversion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mversion to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjg4-w4c6-f6c6 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. ### Patches Patched by version 2.0.0. Previous releases are deprecated in npm. ### Workarounds Make sure to escape git commit messages when using the commitMessage option for the update function.