Skip to main content
HighCodeOWASP A03:2021CWE-79

How to fix: dangerouslySetInnerHTML with computed value

dangerouslySetInnerHTML={{ __html: buildHtml(userInput) }} constructs the HTML string at render time from attacker-controlled parts, defeating any earlier sanitization that operated on the raw field alone.

Why it matters

Computed or concatenated HTML strings can smuggle <script>, <iframe>, or event handlers past component-level sanitizers.

The `code-xss-dangerouslysetinnerhtml-dynamic` check verifies that the server does not expose the `xss-dangerouslysetinnerhtml-dynamic` 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

  1. 1Sanitize the final computed string with DOMPurify before passing it to dangerouslySetInnerHTML.
  2. 2Avoid string concatenation; render React components for trusted structure.
  3. 3Consider Trusted Types policy with require-trusted-types-for 'script'.

Code examples

Sanitize dynamic content before dangerouslySetInnerHTML

TSX
import DOMPurify from "dompurify";

function DynamicContent({ html }: { html: string }) {
  const clean = DOMPurify.sanitize(html, {
    ALLOWED_TAGS: ["p", "strong", "em", "a"],
    ALLOWED_ATTR: ["href"],
  });
  return <div dangerouslySetInnerHTML={{ __html: clean }} />;
}

References

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

See every code check

Questions

How severe is dangerouslySetInnerHTML with computed value?
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 code-xss-dangerouslysetinnerhtml-dynamic, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does dangerouslySetInnerHTML with computed value 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 dangerouslysetinnerhtml with computed value

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

dangerouslySetInnerHTML with computed value fix | VulnRadar