Skip to main content
HighCodeOWASP A03:2021CWE-79

How to fix: document.write DOM XSS Sink

document.write() call detected.

Why it matters

Can completely overwrite page content with attacker-controlled HTML.

document.write is a powerful and dangerous DOM manipulation method.

How to fix it

  1. 1Replace with appendChild or insertAdjacentHTML with sanitization.

Code examples

Never use document.write with user content

JavaScript
// BAD
document.write(userInput);

// GOOD: use DOM APIs to insert content safely
const el = document.createElement("p");
el.textContent = userInput;
document.body.appendChild(el);

References

Detected automatically by VulnRadar. The check id is document-write-sink, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is document.write DOM XSS Sink?
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 document-write-sink, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does document.write DOM XSS Sink 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.

Propose a checkHow a check is built

Scan your own site for document.write dom xss sink

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: document.write DOM XSS Sink | VulnRadar