All vulnerabilities
CVE-2026-113654GHSA-x3q4-9hxx-gx8m

ApostropheCMS sanitize-html: nonTextTags discard region ends early on an implied close, letting <noscript> content render

apostrophecms sanitize-htmlnpmLibraries & packages
CVSS
5.3Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.35%Chance of exploitation activity in the next 30 days, higher than 27% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in2.18.0Fixed versionGitHub
Published20 Oct 2026Updated 20 Oct 2026CVE List

What fixes it

  • 2.18.0sanitize-html, npmGitHubnpm install sanitize-html@2.18.0

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Summary

sanitize-html discards the *content* of every element in nonTextTags. It delimits that region using htmlparser2's close events, and ignores the isImplied flag htmlparser2 passes it. Closing a still-open ancestor from inside a <noscript> makes htmlparser2 unwind its stack past the noscript; the synthetic implied close it emits on the way ends the discard region early, and everything after it is treated as ordinary body content.

A browser with scripting enabled parses <noscript> content as raw text, so the same markup renders as inert text there. The sanitizer therefore emits elements the page itself would not have.

Reproduction

const sanitizeHtml = require("sanitize-html");

sanitizeHtml('<div><noscript></div><img src="http://evil.test/t.gif"></noscript>', {
  allowedTags: ["div", "img"],
  allowedAttributes: { img: ["src"] },
  nonTextTags: ["script", "style", "textarea", "option", "noscript"],
});
// => '<div></div><img src="http://evil.test/t.gif" />'

Chrome, given the same input, renders no <img> — the whole payload is raw text inside the unclosed <noscript>. Verified with Playwright, srcdoc into an iframe so the scripting flag is on.

A <![CDATA[ variant hides the opening tag from the parser entirely and has the same effect:

<p>Hi</p><![CDATA[ x > <noscript>]]><a href="…">Reset your password</a><img src="…beacon.gif"></noscript>

htmlparser2 runs a CDATA token to ]]>; Chrome ends a bogus comment at the first >, so the <noscript> after it is real to the browser and invisible to the parser.

Where the behaviour is

index.js:

  • :154 — nonTextTagsArray (the default list, ['script','style','textarea','option','xmp']).
  • :638 — onclosetag: function (name, isImplied) — receives the flag.
  • :644 — skipTextDepth-- — decrements without consulting isImplied.

Suggested fix

Do not end a discard region on an implied close. htmlparser2 already distinguishes them; the flag is passed and discarded. Something close to:

onclosetag: function (name, isImplied) {
  if (skipText) {
    if (isImplied) return;   // an implied close must not end the region
    skipTextDepth--;
    …

Text from GitHub Advisory Database

Affected versions 4

  • sanitize-html, npm< 2.18.0GitHub
  • apostropheaffected: < 4.33.0CVE List
  • sanitize-htmlaffected: < 2.18.0CVE List
  • sanitize-html, npmfrom first release, fixed in 2.18.0OSV

References 5