# CVE-2020-7389: Sage X3 Syracuse Missing Authentication for Critical Function in Developer Environment

> Authenticated developers can execute OS commands via a script variable in Sage X3, requiring removal of developer environments from production.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-639w-2r2j-2x43

## What is CVE-2020-7389?

CVE-2020-7389 is a medium-severity command injection vulnerability in Sage X3, published on 22 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Sage X3 System CHAINE Variable Script Command Injection. An authenticated user with developer access can pass OS commands via this variable used by the web application. Note, this developer configuration should not be deployed in production.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Sage Syracuse.

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

No fix has been published for CVE-2020-7389 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7389 being exploited?

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

## Other vulnerabilities in Sage X3

- [CVE-2020-7390](https://insights.sbomify.com/CVE-2020-7390/): Sage X3 Syracuse Persistent XSS in Edit User page (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7389 is a medium-severity command injection vulnerability in Sage X3, published on 22 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7389 in the wild and no public exploit code.

Affected product: Sage X3. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-7389/ (Markdown: https://insights.sbomify.com/CVE-2020-7389/index.md)
```

## Sources

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

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