# CVE-2018-8940: XML external entity in n/a

> An attacker can upload a malicious XML file to trigger an XXE vulnerability, potentially reading sensitive data or executing code.

- **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:** 14 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jw37-c6q4-x7h9

## What is CVE-2018-8940?

CVE-2018-8940 is a critical vulnerability in n/a, published on 14 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ClientServiceConfigController.cs in Enghouse Cloud Contact Center Platform 7.2.5 has functionality for loading external XML files and parsing them, allowing an attacker to upload a malicious XML file and reference it in the URL of the application, forcing the application to load and parse the malicious XML file, aka an XXE issue.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Enghouse Contact Center\.

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

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

## Is CVE-2018-8940 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8940 is a critical vulnerability in n/a, published on 14 May 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-8940 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-8940/ (Markdown: https://insights.sbomify.com/CVE-2018-8940/index.md)
```

## Sources

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

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