How to fix: Server-Side XML Parsing Detected
Server-side XML parsing library usage found. Ensure external entity processing is disabled.
Why it matters
If external entities are not disabled, XXE attacks can read local files or perform SSRF.
Server-side XML parsers can be vulnerable to XXE if not properly configured.
How to fix it
- 1Disable external entity processing.
- 2Validate that noent: false and nonet: true are set.
- 3Consider using JSON instead of XML.
Code examples
Safe xml2js config
const parser = new xml2js.Parser({ strict: true, normalize: true, xmlns: false });References
Detected automatically by VulnRadar. The check id is xxe-server-xml, 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 Server-Side XML Parsing Detected?
- VulnRadar rates this medium 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 xxe-server-xml, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server-Side XML Parsing Detected 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.