SILVERSTRIPE/FRAMEWORK · CVE-2026-88988 · Package
FIX → 6.2.13
Silverstripe Framework's HTML sanitiser fails to strip SVG data URIs from stored CMS content, and SVG can run script. A CMS author can save such content so that JavaScript runs in the browser of another user who views the page.
first public Oct 29, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running Silverstripe Framework before 6.2.13 where CMS authors can save HTML content that other users view. Exposure depends on who can edit content and whether viewers are logged in to sensitive areas. Sites with only trusted editors or static output have less exposure.
Not affected if framework-6.2.13-or-later, no-untrusted-content-editors
Who cares cms, php, self-hosted, silverstripe
composer show silverstripe/frameworksilverstripe/framework in composer.lock and confirm the version is below 6.2.13Upgrade to 6.2.13
silverstripe/framework upgrade to Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove SVG data URIs from stored CMS content even though SVG documents can execute script. A CMS author can save such content, and JavaScript executes in the browser of another user who views it. This issue is fixed in version 6.2.13.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
6.2.13NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.