How to fix: document.write with JSON.parse(userInput)
Combining document.write with JSON.parse(userInput) reflects attacker-controlled string values straight into the document, where any <script> or on* attribute is executed before any sanitizer can intercept it.
Why it matters
document.write runs synchronously during parse; injected scripts execute in the page origin and persist.
The `code-xss-documentwrite-jsonparse` check verifies that the server does not expose the `xss-documentwrite-jsonparse` 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
- 1Never reflect parsed user JSON into document.write.
- 2Render values via textContent into a known-safe container after DOMContentLoaded.
- 3Add a strict CSP with script-src 'self' to block inline injection.
Code examples
Never write parsed JSON into the document
// BAD: parsed JSON value written into the DOM
const data = JSON.parse(serverResponse);
document.write(data.htmlContent);
// GOOD: use DOM APIs with textContent
const el = document.getElementById("output");
el.textContent = data.textContent;References
Detected automatically by VulnRadar. The check id is code-xss-documentwrite-jsonparse, 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 document.write with JSON.parse(userInput)?
- VulnRadar rates this critical 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-documentwrite-jsonparse, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does document.write with JSON.parse(userInput) 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.