CDATA variant of GHSA-x3q4-9hxx-gx8m still bypasses the noscript discard in sanitize-html 2.18.1

published 2026-11-11 18h ago modified 2026-11-11 18h ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository apostrophecms/apostrophe. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Security advisory published by the maintainers of apostrophecms/apostrophe for sanitize-html: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

fixed in 1

npm sanitize-html 2.18.2

Is GHSA-2rjc-9xvg-45j7 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	sanitize-html	<2.18.2	2.18.2

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-436 Interpretation Conflict

References

github.com /apostrophecms/apostrophe/security/advisories/GHSA-2rjc-9xvg-45j7
advisory

Sources

Maintainer advisory GHSA-2rjc-9xvg-45j7

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of apostrophecms/apostrophe published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.