CVE-2026-113654: apostrophecms apostrophe · Cross-site Scripting
Affects apostrophecms apostropheSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.33.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.33.0, 2.18.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade apostrophe to 4.33.0; sanitize-html to 2.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| apostrophecmsapostrophe | Affected
| Fixed in
|
| apostrophecmssanitize-html | Affected
| Fixed in
|
npmsanitize-htmlpkg:npm/sanitize-htmlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade sanitize-html to version 2.18.0 or later to address the improper sanitization of the noscript tag. Additionally, upgrade ApostropheCMS to version 4.33.0 or later where this fix is incorporated. No other specific mitigations are indicated. Patch status is confirmed by the vendor advisory indicating the fix in sanitize-html 2.18.0.
Description
ApostropheCMS versions prior to 4.33.0 are affected by a cross-site scripting (XSS) vulnerability due to improper sanitization of HTML content involving the noscript tag. This issue arises from the sanitize-html library versions before 2.18.0, where the non-default nonTextTags configuration including noscript can prematurely end discard regions, allowing potentially malicious content to survive sanitization and render in browsers. The vulnerability is fixed in sanitize-html version 2.18.0.
References
- github.com/apostrophecms/apostrophe/security/advisories/GHSA-x3q4-9hxx-gx8m (opens in a new tab)
- github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (opens in a new tab)
- github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350 (opens in a new tab)
- github.com/apostrophecms/apostrophe/releases/tag/sanitize-html@2.18.0 (opens in a new tab)