SILVERSTRIPE/FRAMEWORK · CVE-2026-88987 · Package
FIX → 6.2.13
The HTML sanitiser in Silverstripe Framework fails to strip script-capable XHTML and XML data URIs from stored content. A CMS author can save such content, and JavaScript runs in the browser of any other user who views it.
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 content that other users view. The risk is stored script injection into the browsers of people who view that content, so sites where only trusted editors can write content carry less risk. Sites on 6.2.13 or later are not affected.
Not affected if no-untrusted-content-authors, version-6.2.13-or-later
Who cares cms, php, self-hosted, silverstripe
composer show silverstripe/frameworksilverstripe/framework versions below 6.2.13 in composer.lockUpgrade to 6.2.13
6.2.13Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove script-capable XHTML and XML data URIs from stored CMS content. 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.
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.