CVE-2026-44990: Apostrophe has default XSS via `xmp` raw-text passthrough in `sanitize-html`
ApostropheCMS is an open-source Node.js content management system, and sanitize-html provides a simple HTML sanitizer with a clear API. Under the default configuration, versions of `sanitize-html` prior to 2.17.4 can turn attacker-controlled content inside a disallowed `xmp` element into live HTML or JavaScript. This is a sanitizer bypass in the default `disallowedTagsMode: 'discard'` path and can lead to stored XSS in applications that render sanitized output back to users. Version 2.17.4 patches the issue.
Security readout for executives and security teams
Plain-English summary
Applications using vulnerable sanitize-html may think they removed unsafe markup, but content inside a blocked xmp tag can become active HTML or JavaScript. If untrusted content is saved and later viewed, this can become stored XSS affecting users who open the content.
Executive priority
Treat as urgent for public-facing CMS, collaboration, support, or profile systems that store user content. The issue can turn a security control into a bypass, enabling browser-side compromise when users view attacker-supplied content.
Technical view
sanitize-html versions before 2.17.4 have a default sanitizer bypass in disallowedTagsMode: discard. Attacker-controlled content inside a disallowed xmp raw-text element can be emitted as live markup or script. The CVE is CWE-79 with CVSS 9.3, network attack vector, low complexity, no privileges, and user interaction required.
Likely exposure
Highest exposure is Node.js or ApostropheCMS-adjacent applications using sanitize-html below 2.17.4 to process user-supplied HTML and render sanitized output. Downstream Red Hat advisories indicate packaged ecosystem tracking, but exact product exposure should be verified from those advisories.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a victim to view rendered sanitized content, but stored XSS can still create serious account, data, and session exposure in the affected origin.
Researcher notes
Focus validation on sanitizer configuration and rendering paths, not only package presence. The reported weakness is in the default discard behavior for disallowed xmp elements. Do not assume exploitability where sanitized output is never rendered to users.
Mitigation direction
Upgrade sanitize-html to version 2.17.4 or later.
Update lockfiles and redeploy all services bundling vulnerable sanitize-html versions.
Check Red Hat advisories if consuming sanitize-html through Red Hat-maintained packages.
Review vendor guidance for any additional application-specific mitigations.
Prioritize systems accepting rich text, CMS content, comments, or profile HTML.
Validation and detection
Inventory direct and transitive sanitize-html package versions.
Confirm no deployed artifact contains sanitize-html below 2.17.4.
Map where user-controlled HTML is sanitized and later rendered.
Review CMS and rich-text workflows for stored content exposure.
Track Red Hat CVE and errata status for managed platforms.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
12Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.