---
id: "CVE-2026-91113"
page: "https://infrastack.ai/live/CVE-2026-91113"
kind: "vulnerability"
aliases: ["CVE-2026-91113", "GHSA-4qv2-g5vp-wjjw"]
title: "Silverstripe Framework: User-controlled ClassName allows unauthorized record type change"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "silverstripe/framework", "fixed": ["6.2.13"], "affected": "< 6.2.13", "ecosystem": "composer"}]
ecosystems: ["composer"]
tags: ["cms", "cwe-862", "package", "php", "runtime", "silverstripe"]
not_affected_if: ["auth-required", "no-cms-editors"]
published_at: "2026-11-16T17:17:36+00:00"
first_seen_at: "2026-11-16T17:37:59+00:00"
updated_at: "2026-11-16T22:38:28+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-91113", "first_seen_at": "2026-11-16T17:37:59+00:00"}, {"source": "ghsa", "url": "https://github.com/advisories/GHSA-4qv2-g5vp-wjjw", "first_seen_at": "2026-11-16T22:38:02+00:00"}]
exploit_sources: []
---

# Silverstripe Framework: User-controlled ClassName allows unauthorized record type change

Link for people: https://infrastack.ai/live/CVE-2026-91113 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- composer:silverstripe/framework affected < 6.2.13 fixed 6.2.13

## How to check

- Check the installed version: `composer show silverstripe/framework`
- Look for a `silverstripe/framework` version below `6.2.13` in `composer.lock`

## Fix

- `silverstripe/framework` to `6.2.13` or later

## Timeline

- 2026-11-16T17:37:59+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-91113
- 2026-11-16T22:38:02+00:00 ghsa https://github.com/advisories/GHSA-4qv2-g5vp-wjjw

## Documents

- [advisory] Vendor advisory: github.com https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-4qv2-g5vp-wjjw
- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/silverstripe/silverstripe-framework/security-advisories/GHSA-4qv2-g5vp-wjjw
- [fix] Patch: github.com https://github.com/silverstripe/silverstripe-framework/commit/8b6e9c4514cbe37feeaf9ddddf796a3109448187
- [fix] Release notes: github.com https://github.com/silverstripe/silverstripe-framework/releases/tag/6.2.13
- [fix] Patch: github.com https://github.com/silverstripe/silverstripe-framework/pull/12042

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
