Skip to main content
MediumCodeOWASP A03:2021CWE-79

How to fix: innerHTML DOM XSS Sink

Multiple innerHTML assignments detected.

Why it matters

User input reaching innerHTML can execute arbitrary scripts.

innerHTML parses and executes HTML, making it a common XSS vector.

How to fix it

  1. 1Use textContent for text, or sanitize HTML before assignment.

Code examples

Use textContent instead of innerHTML

JavaScript
// BAD: executes scripts in user content
element.innerHTML = userInput;

// GOOD: text only, no script execution
element.textContent = userInput;

// If you need HTML, sanitize with DOMPurify
import DOMPurify from "dompurify";
element.innerHTML = DOMPurify.sanitize(userInput);

References

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

See every code check

Questions

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