Read the docs

Silverstripe Framework lets users change record type without checks

Priority LOW 17CWE-862Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-862.

Summary

Silverstripe Framework before 6.2.13 is affected. Its GridField detail form does not check permissions for the target class when a record's class is changed (CWE-862). A CMS user with edit access to a record through that form can change it into an unrelated class. This bypasses the create and edit permission checks required for the target class.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

Description from the CNA

Silverstripe 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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix Fixed silverstripe-framework (silverstripe): 6.2.13silverstripe/framework (Packagist): 6.2.13

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
silverstripesilverstripe-frameworkbefore 6.2.136.2.13Patch availableCNA
—silverstripe/framework (Packagist)before 6.2.136.2.13Patch availableGHSA-4qv2-g5vp-wjjw
  • silverstripe-framework Vendorsilverstripe Affected before 6.2.13 Fixed in 6.2.13 Patch available CNA
  • silverstripe/framework (Packagist) Vendor— Affected before 6.2.13 Fixed in 6.2.13 Patch available GHSA-4qv2-g5vp-wjjw

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:silverstripe:framework:*:*:*:*:*:*:*:*——silverstripe
  • cpe:2.3:a:silverstripe:framework:*:*:*:*:*:*:*:* Versions — — ·silverstripe

Remediation

Upgrade silverstripe-framework and silverstripe/framework to version 6.2.13.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

  • Fix · CNA silverstripe-framework (silverstripe) Fixed in 6.2.13
  • Fix · GHSA-4qv2-g5vp-wjjw silverstripe/framework (Packagist) Fixed in 6.2.13 Advisory →

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-91113
  2. 2026-11-16 CISA SSVC decision points changed
  3. 2026-11-16 Alias added: GHSA-4qv2-g5vp-wjjw
  4. 2026-11-16 Fix available: Packagist/silverstripe/[email protected] · GHSA-4qv2-g5vp-wjjw
  5. 2026-11-16 CVSS score added · GHSA-4qv2-g5vp-wjjw
  6. 2026-11-16 Weakness changed · GHSA-4qv2-g5vp-wjjw
  7. 2026-11-16 8 new references · GHSA-4qv2-g5vp-wjjw

References

  • TI-2007-02239 Unspecified vulnerability in the search functionality in SilverStripe 2.0.0 has unknown impact and attack vectors. CVSS 2.0HIGH 10.0
  • TI-2026-92196 Privilege escalation in Silverstripe Framework CMS_ACCESS_SecurityAdmin CVSS 3.1MEDIUM 6.8
  • TI-2019-09110 In SilverStripe through 4.3.3, a missing warning about leaving install.php in a public… CVSS 3.1CRITICAL 9.8
  • TI-2019-09070 SQL injection vulnerability in silverstripe/restfulserver module 1.0.x before 1.0.9… CVSS 3.0CRITICAL 9.8
  • TI-2019-04049 All versions of SilverStripe 3 prior to 3.6.7 and 3.7.3, and all versions of SilverStripe… CVSS 3.0CRITICAL 9.8
  • TI-2026-92199 Cross-site scripting in Silverstripe Framework via control bytes CVSS 3.1MEDIUM 6.4
See all 105 →

Sources