# CVE-2018-19858: PrinceXML, versions 10 and below, is vulnerable to XXE due to the lack of protection against external entities.


- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-67m6-wgh8-4vh7

## What is CVE-2018-19858?

CVE-2018-19858 is a high-severity vulnerability in n/a, published on 29 Jan 2019. 

### Official description

PrinceXML, versions 10 and below, is vulnerable to XXE due to the lack of protection against external entities. If an attacker passes HTML referencing an XML file (e.g., in an IFRAME element), PrinceXML will fetch the XML and parse it, thus giving an attacker file-read access and full-fledged SSRF.

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

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

It affects 1 product.


Products: Princexml Princexml.

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

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

## Is CVE-2018-19858 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19858 is a high-severity vulnerability in n/a, published on 29 Jan 2019. 
Exploitation: There is no known exploitation of CVE-2018-19858 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-19858/ (Markdown: https://insights.sbomify.com/CVE-2018-19858/index.md)
```

## Sources

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

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