CVE-2018-19858
PrinceXML, versions 10 and below, is vulnerable to XXE due to the lack of protection against external entities.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.60%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.0
- 8.6 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- EPSS
- 2.60% probability · 85th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-611
- Affected
- princexml/princexml
- Source
- cve@mitre.org
EPSS 2.6% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://hacking.us.com/blog/XSS-to-XXE-in-Prince/Exploit, Third Party Advisory
- https://www.lynxsecurity.io/Third Party Advisory
- https://www.youtube.com/watch?v=-7YIzYtWhzMExploit, Third Party Advisory
- https://hacking.us.com/blog/XSS-to-XXE-in-Prince/Exploit, Third Party Advisory
- https://www.lynxsecurity.io/Third Party Advisory
- https://www.youtube.com/watch?v=-7YIzYtWhzMExploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.