CVE-2026-91110 · Package
NO FIX YET · SEE WHAT TO DO
Silverstripe Framework's HTML sanitiser fails to normalise certain control bytes that browsers ignore when parsing URLs, so a javascript: scheme can slip past it. A CMS author can store such content, and JavaScript then runs in the browser of any user who views it.
first public Oct 29, 2026 · 1 source
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 or other users can store HTML that is later shown to other users. Exposure depends on who can edit content, so sites with only trusted editors carry less risk. Sites that have already upgraded, or that do not use Silverstripe CMS, can skip it.
Not affected if fixed-version, no-untrusted-content-editors
Who cares cms, php, silverstripe
composer.lock or with composer show silverstripe/framework6.2.13Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not normalize certain control bytes that browsers ignore when parsing URLs. A CMS author can place those bytes before a javascript: URL in stored content so the sanitiser misses the dangerous scheme, and JavaScript executes in the browser of another user who views the content. 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. Posts quoted belong to their authors.