# CVE-2018-20768: Code injection in n/a

> Attackers can execute arbitrary PHP code on Xerox multifunction printers by exploiting a writable file vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-phqx-688p-m9x2

## What is CVE-2018-20768?

CVE-2018-20768 is a critical code injection vulnerability in n/a, published on 10 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Xerox WorkCentre 3655, 3655i, 58XX, 58XXi, 59XX, 59XXi, 6655, 6655i, 72XX, 72XXi, 78XX, 78XXi, 7970, 7970i, EC7836, and EC7856 devices before R18-05 073.xxx.0487.15000. An attacker can execute PHP code by leveraging a writable file.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-20768?

It affects 29 products.


Products: Xerox Workcentre 3655 Firmware, Xerox Workcentre 3655i Firmware, Xerox Workcentre 5845 Firmware, Xerox Workcentre 5865 Firmware, Xerox Workcentre 5865i Firmware, Xerox Workcentre 5875 Firmware, Xerox Workcentre 5875i Firmware, Xerox Workcentre 5890 Firmware, Xerox Workcentre 5890i Firmware, Xerox Workcentre 5900 Firmware, Xerox Workcentre 5900i Firmware, Xerox Workcentre 6655 Firmware, Xerox Workcentre 6655i Firmware, Xerox Workcentre 7220 Firmware, Xerox Workcentre 7220i Firmware, Xerox Workcentre 7225 Firmware, Xerox Workcentre 7225i Firmware, Xerox Workcentre 7830 Firmware, Xerox Workcentre 7830i Firmware, Xerox Workcentre 7835 Firmware and 9 more.

## How do I fix CVE-2018-20768?

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

## Is CVE-2018-20768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-11061](https://insights.sbomify.com/CVE-2016-11061/): Command injection in n/a (critical 9.8)
- [CVE-2018-20770](https://insights.sbomify.com/CVE-2018-20770/): SQL injection in n/a (critical 9.8)
- [CVE-2018-20771](https://insights.sbomify.com/CVE-2018-20771/): Command injection in n/a (critical 9.8)
- [CVE-2020-9330](https://insights.sbomify.com/CVE-2020-9330/): Missing authorization in n/a (high 8.8)
- [CVE-2018-20767](https://insights.sbomify.com/CVE-2018-20767/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20768 and fix it if it is affected.

What it is: CVE-2018-20768 is a critical code injection vulnerability in n/a, published on 10 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20768 in the wild and no public exploit code.

Affected product: n/a. 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-2018-20768/ (Markdown: https://insights.sbomify.com/CVE-2018-20768/index.md)
```

## Sources

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

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