How to fix: DOMParser.parseFromString user HTML
new DOMParser().parseFromString(userInput, 'text/html') parses arbitrary HTML into a Document. Subsequent node import via adoptNode or document.importNode preserves <script> elements, which can execute when reattached.
Why it matters
Scripts parsed via DOMParser can survive adoption into the host document and execute.
The `code-xss-domparser-parsefromstring` check verifies that the server does not expose the `xss-domparser-parsefromstring` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Sanitize the parsed result with DOMPurify before adopting any nodes.
- 2Strip <script> elements after parseFromString.
- 3Prefer textContent rendering to direct DOM adoption.
Code examples
DOMParser is safe for XML parsing but not HTML injection
// DOMParser.parseFromString(html, "text/html") creates a document,
// safe for parsing, dangerous if you then inject the result into the live DOM.
const doc = parser.parseFromString(userHtml, "text/html");
// Never do: document.body.appendChild(doc.body) without sanitization
// GOOD: extract only text content
const text = doc.body.textContent;
// Or sanitize with DOMPurify before appendingReferences
Detected automatically by VulnRadar. The check id is code-xss-domparser-parsefromstring, 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 DOMParser.parseFromString user HTML?
- VulnRadar rates this medium 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 code-xss-domparser-parsefromstring, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DOMParser.parseFromString user HTML map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03: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.