How to fix: SVG with external entity reference (XXE)
An <svg> with an external entity reference like <!ENTITY xxe SYSTEM "file:///..."> can leak local files when the SVG is rendered server-side.
Why it matters
Strip DOCTYPE and external entities when ingesting SVG; use a hardened parser
An <svg> with an external entity reference like <!ENTITY xxe SYSTEM "file:///..."> can leak local files when the SVG is rendered server-side.
How to fix it
- 1Strip DOCTYPE and external entities when ingesting SVG; use a hardened parser
Code examples
Disable external entity references in SVG parsing
// When parsing SVG server-side, disable external references
import { XMLParser } from "fast-xml-parser";
const parser = new XMLParser({
processEntities: false,
ignoreDeclaration: true,
});
// Never load external ENTITY references from user-supplied SVGReferences
Detected automatically by VulnRadar. The check id is svg-external-entity-reference, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is SVG with external entity reference (XXE)?
- VulnRadar rates this critical severity in the content 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 svg-external-entity-reference, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does SVG with external entity reference (XXE) 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.