SILVERSTRIPE/FRAMEWORK · CVE-2026-91113 · Package
FIX → 6.2.13
A CMS user who can edit a record through a GridField detail form can submit a ClassName value to turn that record into an unrelated class. The change skips the create and edit permission checks for the target class, so the user can alter records outside their intended model hierarchy.
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 the Silverstripe CMS on Silverstripe Framework before 6.2.13 where CMS editors can edit records through GridField detail forms. The attacker needs a CMS login with edit rights on the record, so sites without that kind of CMS user are lower risk.
Not affected if auth-required, no-cms-editors
Who cares cms, php, runtime, silverstripe
composer show silverstripe/frameworksilverstripe/framework version below 6.2.13 in composer.lockUpgrade to 6.2.13
silverstripe/framework to 6.2.13 or laterSilverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit a record through a GridField detail form can submit a user-controlled ClassName value to change the record into an unrelated class without the create and edit permission checks required for that target class. This permits an unauthorized record type change outside the GridField's intended model hierarchy. 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.