CVE-2020-7730 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in bestzip. A fix is available for bestzip — see the affected versions and patch details below.
Command injection in bestzip
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-7730 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
bestzipnpmDescription
The package bestzip before 2.1.7 are vulnerable to Command Injection via the options param.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | bestzip | all versions | 2.1.7npm install bestzip@2.1.7 |
Affected Products
bestzipbestzip_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bestzip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bestzip to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7730 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
Is CVE-2020-7730 in your dependencies?
Find it across npm, including transitive dependencies.