How to fix: XML external entity (XXE) risk
XML is being parsed without explicit external entity restrictions.
Why it matters
An XXE attack using a crafted XML payload can read server-side files, make SSRF requests, or cause denial-of-service via recursive entity expansion (billion laughs attack).
XML parsers that allow SYSTEM/PUBLIC entities can be abused to load external content at the server level.
How to fix it
- 1Set processEntities: false in fast-xml-parser
- 2Disable DOCTYPE declarations at the parser level
- 3Validate XML against a strict schema before parsing
Code examples
Harden XML parsing against XXE
import { XMLParser } from "fast-xml-parser";
const parser = new XMLParser({
processEntities: false,
ignoreDeclaration: true,
});
// Never pass user-controlled XML to parsers with external entity support enabledReferences
Detected automatically by VulnRadar. The check id is xml-external-entity, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is XML external entity (XXE) risk?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id xml-external-entity, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does XML external entity (XXE) risk map to?
- It maps to CWE-611. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.