Skip to main content
VulnerabilityPublished

CVE-2026-88988: Silverstripe Framework · XSS via SVG data URI

Affects silverstripe/frameworkSource GCVE Database

0
Compare
Authoritative record:CVE-2026-88988· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade to 6.2.13 when convenient.

Data as of 16 Nov 2026, 23:52 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.4
Patch
Available – fixed in 6.2.13
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade silverstripe/framework to 6.2.13.

Affected software

ProductAffectedFixed in
Packagistsilverstripe/frameworkAffected
  • <6.2.13
Fixed in
  • 6.2.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Silverstripe Framework to version 6.2.13 or later, where the vulnerability is fixed. Applying this official patch fully mitigates the issue.

Description

A cross-site scripting (XSS) vulnerability exists in Silverstripe Framework versions prior to 6.2.13 due to the HTML sanitizer not removing SVG data URIs. This allows a CMS author to store content that executes JavaScript in the browsers of other users who view the content. The issue is fixed in version 6.2.13.

References

Community reviews

Loading reviews…