Skip to main content
MediumCodeOWASP A03:2021CWE-79

How to fix: insertAdjacentHTML DOM Sink

insertAdjacentHTML() usage detected.

Why it matters

Can inject HTML at various positions in the DOM.

Like innerHTML, this method parses HTML strings.

How to fix it

  1. 1Sanitize input or use insertAdjacentText for text-only insertion.

Code examples

Avoid insertAdjacentHTML with user content

JavaScript
// BAD
element.insertAdjacentHTML("beforeend", userInput);

// GOOD: use insertAdjacentText for text-only
element.insertAdjacentText("beforeend", userInput);

// Or if HTML is needed, sanitize first
import DOMPurify from "dompurify";
element.insertAdjacentHTML("beforeend", DOMPurify.sanitize(userInput));

References

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

See every code check

Questions

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