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

> An XXE vulnerability in SDL Web Content Manager allows attackers to read sensitive files from the system.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-42gh-7xp2-q72c

## What is CVE-2018-19371?

CVE-2018-19371 is a medium-severity vulnerability in n/a, published on 2 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SaveUserSettings service in Content Manager in SDL Web 8.5.0 has an XXE Vulnerability that allows reading sensitive files from the system.

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

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

It affects 1 product.


Products: Sdl Web Content Manager.

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

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

## Is CVE-2018-19371 being exploited?

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

Public exploit code:

- SDL Web Content Manager 8.5.0 - XML External Entity Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19371 is a medium-severity vulnerability in n/a, published on 2 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19371 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-19371/ (Markdown: https://insights.sbomify.com/CVE-2018-19371/index.md)
```

## Sources

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

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