CVE-2026-88989: CVE-2026-88989: Authorization Bypass in Silverstripe Framework GridFieldDetailForm
CVE-2026-88989: Authorization Bypass in Silverstripe Framework GridFieldDetailForm Vulnerability ID: CVE-2026-88989 CVSS Score: 4.3 Published: 2026-11-16 CVE-2026-88989 (tracked as GHSA-3qh3-54qg-gpq3) is a missing
CVE-2026-88989: Authorization Bypass in Silverstripe Framework GridFieldDetailForm
Vulnerability ID: CVE-2026-88989
CVSS Score: 4.3
Published: 2026-11-16
CVE-2026-88989 (tracked as GHSA-3qh3-54qg-gpq3) is a missing authorization vulnerability (CWE-862) in the Silverstripe Framework affecting versions prior to 6.2.13. The flaw exists within the GridFieldDetailForm_ItemRequest request handler, which orchestrates record creation and editing workflows inside the Silverstripe CMS backend. Specifically, the server-side persistence method saveFormIntoRecord() fails to verify whether an authenticated user possesses the necessary creation permissions (canCreate) when processing an unpersisted DataObject record.
Consequently, a low-privileged CMS user who has permission to access a GridField interface and edit existing records can bypass role-based creation restrictions. By sending a crafted HTTP POST request directly to the item/new endpoint with the action_doSave parameter, the user can instantiate and persist unauthorized database records. The vulnerability is rated Medium severity with a CVSS v3.1 base score of 4.3 and is remediated in Silverstripe Framework version 6.2.13.
TL;DR
An authorization bypass in Silverstripe Framework (< 6.2.13) allows authenticated CMS users without model creation permissions to create new database records by sending direct POST requests to the GridFieldDetailForm save endpoint. Upgrade to version 6.2.13 to remediate the flaw.
⚠️ Exploit Status: POC
Technical Details
- Vulnerability ID: CVE-2026-88989 / GHSA-3qh3-54qg-gpq3
- Weakness Class: CWE-862: Missing Authorization
- CVSS v3.1 Score: 4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Affected Component: GridFieldDetailForm_ItemRequest::saveFormIntoRecord()
- Affected Versions: silverstripe/silverstripe-framework < 6.2.13
- Patched Version: silverstripe/silverstripe-framework 6.2.13
- Impact: Unauthorized creation of DataObject records by low-privileged CMS users
- Exploit Status: PoC available in vendor test suite; Not listed in CISA KEV
Affected Systems
- Silverstripe Framework (silverstripe/silverstripe-framework)
- Silverstripe CMS
-
silverstripe/silverstripe-framework: < 6.2.13 (Fixed in:
6.2.13)
Code Analysis
Commit: 693c948
[CVE-2026-88989] Auth bypass GridFieldDetailForm (#12043)
File: lang/en.yml
@@ -174,6 +174,7 @@ en:
Save: Save
Saved: 'Saved {name} {link}'
SilverStripe\Forms\GridField\GridFieldDetailForm_ItemRequest:
+ CreatePermissionsFailure: 'It seems you don''t have the necessary permissions to create "{ObjectTitle}"'
EditPermissionsFailure: 'It seems you don''t have the necessary permissions to edit "{ObjectTitle}"'
NEW: 'Add new record'
NEXT: 'Go to next record'
File: src/Forms/GridField/GridFieldDetailForm_ItemRequest.php
@@ -821,6 +821,17 @@ public function httpError($errorCode, $errorMessage = null)
*/
protected function saveFormIntoRecord($data, $form)
{
+ if (!$this->record->ID
+ && (!$this->record->hasMethod('canCreate') || !$this->record->canCreate(null, $this->getCreateContext()))
+ ) {
+ $this->httpError(403, _t(
+ __CLASS__ . '.CreatePermissionsFailure',
+ 'It seems you don\'t have the necessary permissions to create "{ObjectTitle}"',
+ ['ObjectTitle' => $this->getModelName()]
+ ));
+ return null;
+ }
+
$list = $this->gridField->getList();
// Check object matches the correct classname
Exploit Details
- GitHub: Official functional regression test (GridFieldDetailFormCreatePermissionTest.php) demonstrating the authorization bypass via a direct POST request with action_doSave=1.
Mitigation Strategies
- Upgrade silverstripe/silverstripe-framework to version 6.2.13 or later to enforce server-side canCreate() checks inside GridFieldDetailForm_ItemRequest::saveFormIntoRecord().
- Implement temporary model-level validation in DataObject::onBeforeWrite() to verify !$this->isInDB() && !$this->canCreate() where immediate patching is not feasible.
- Restrict network access to the Silverstripe CMS administrative backend (/admin/*) to trusted IP ranges or VPN connections.
- Audit CMS user roles and permissions to ensure only trusted users have access to ModelAdmin and GridField interfaces.
Remediation Steps:
- Run 'composer update silverstripe/silverstripe-framework --with-dependencies' in the project root directory.
- Verify the updated package version by executing 'composer show silverstripe/silverstripe-framework' and confirming it is 6.2.13 or higher.
- Flush the Silverstripe manifest cache by running 'vendor/bin/sake dev/build flush=all' to ensure updated framework classes and language files are loaded.
- Review HTTP access logs for POST requests to '*/item/new/ItemEditForm' and audit database tables for unauthorized records created by low-privileged CMS accounts.
References
- GitHub Security Advisory: GHSA-3qh3-54qg-gpq3
- Silverstripe Framework Pull Request #12043
- Patch Commit 693c948bae13dd2a854489baa575123ca3e60155
- Silverstripe Framework Release 6.2.13
- Silverstripe Security Release Advisory: CVE-2026-88989
- National Vulnerability Database (NVD): CVE-2026-88989
- CVE.org Record: CVE-2026-88989
- CVEListV5 JSON Record: CVE-2026-88989
Read the full report for CVE-2026-88989 on our website for more details including interactive diagrams and full exploit analysis.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.