Skip to main content
MediumCodeOWASP A03:2021CWE-79

How to fix: outerHTML DOM XSS Sink

outerHTML assignment detected.

Why it matters

Similar to innerHTML, can execute arbitrary scripts.

outerHTML replaces the element entirely with parsed HTML.

How to fix it

  1. 1Avoid outerHTML with user input, use safe DOM methods.

Code examples

Avoid outerHTML with user content

JavaScript
// BAD
element.outerHTML = userContent;

// GOOD: use replaceWith() with a safe text node
const text = document.createTextNode(userContent);
element.replaceWith(text);
// Or create structured elements programmatically

References

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

See every code check

Questions

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