CVE-2026-91114 · Package
NO FIX YET · SEE WHAT TO DO
Silverstripe Framework's PermissionCheckboxSetField saves permission codes without checking them against an allowlist and renders them without escaping. A user with access to the Security section can store script that runs in the browser of another user who views that field.
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 users can edit permissions in the Security section. Another admin viewing the affected field can trigger the script. Sites that do not use the Security section for permission editing are less exposed.
Not affected if version-6.2.13-or-later
Who cares cms, php, silverstripe
silverstripe/framework version in composer.lock or with composer show silverstripe/frameworksilverstripe/framework 6.2.13Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, PermissionCheckboxSetField accepts permission codes that the field did not offer and stores them without an allowlist, then renders permission codes without escaping them. A user with access to the Security section can save attacker-controlled content as a permission code, causing JavaScript to execute in the browser of another user who views the field. This issue is fixed in version 6.2.13.
This page as .md ·
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.