CVE-2020-7712 is a high-severity (CVSS 7.2) OS Command Injection vulnerability in org.webjars.npm:json. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.webjars.npm:json — see the affected versions and patch details below.
trentm/json vulnerable to command injection
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-7712 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
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.
jsonnpmDescription
This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars.npm:json | all versions | No fix |
| 📦npm | json | all versions | 10.0.0npm install json@10.0.0 |
Affected Products
jsonjoyentcommerce guided searchoraclefinancial services crime and compliance management studiooraclefinancial services regulatory reporting with agilereporteroracletimesten in-memory databaseoracleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:json, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.webjars.npm:json has shipped for CVE-2020-7712 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-7712 in your dependencies?
Find it across Maven, npm, including transitive dependencies.