# CVE-2020-7712: Command Injection


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Aug 2020
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-3c6g-pvg8-gqw2, MINI-6mqm-xf97-3r7q

## What is CVE-2020-7712?

CVE-2020-7712 is a high-severity vulnerability in Oracle Commerce Guided Search, published on 30 Aug 2020. 

### Official description

This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2020-7712?

4 open source packages ship an affected version, including org.webjars.npm:json and json. It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.webjars.npm:json` | Maven | All versions to 9.0.6 | None |
| `org.webjars.npm:json` | Maven | All versions to 9.0.6 | None |
| `json` | npm | All versions | 10.0.0 |
| `json` | npm | All versions | 10.0.0 |

Products: Joyent Json, Oracle Commerce Guided Search, Oracle Financial Services Crime and Compliance Management Studio, Oracle Financial Services Regulatory Reporting With Agilereporter, Oracle Timesten In-Memory Database.

## How do I fix CVE-2020-7712?

Upgrade to a fixed version.

## Is CVE-2020-7712 being exploited?

There is no known exploitation of CVE-2020-7712 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7712 and fix it if it is affected.

What it is: CVE-2020-7712 is a high-severity vulnerability in Oracle Commerce Guided Search, published on 30 Aug 2020. 
Exploitation: There is no known exploitation of CVE-2020-7712 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.webjars.npm:json (Maven): affected all versions up to 9.0.6; no fix listed
- org.webjars.npm:json (Maven): affected all versions up to 9.0.6; no fix listed
- json (npm): affected all versions; fixed in 10.0.0
- json (npm): affected all versions; fixed in 10.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7712/ (Markdown: https://insights.sbomify.com/CVE-2020-7712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7712
- OSV: https://osv.dev/vulnerability/CVE-2020-7712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7712/
Summaries are generated and may contain mistakes; the official description above is the record.