DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-91112: CVE-2026-91112: Privilege Escalation via CMS_ACCESS_SecurityAdmin in Silverstripe Framework

CVE-2026-91112: Privilege Escalation via CMS_ACCESS_SecurityAdmin in Silverstripe Framework

Vulnerability ID: CVE-2026-91112
CVSS Score: 6.8
Published: 2026-11-16

Silverstripe Framework prior to version 6.2.13 contains an improper privilege management vulnerability (CWE-269) within the Group authorization and validation logic. A delegated administrator possessing the CMS_ACCESS_SecurityAdmin permission, but lacking full ADMIN privileges, can edit or reparent groups that acquire administrative capabilities indirectly via permission roles or ancestor inheritance. By adding their own account to such a group or moving a controlled group underneath a role-privileged parent, the user escalates to full administrative access across the CMS.

TL;DR

Authenticated Silverstripe users with delegated Security Admin permissions (CMS_ACCESS_SecurityAdmin) can escalate to full ADMIN privileges by modifying or reparenting groups that derive administrative rights through roles or hierarchical inheritance. Upgrading silverstripe/framework to version 6.2.13 resolves the flaw.


Technical Details

  • Vulnerability ID: CVE-2026-91112 / GHSA-rg72-5958-c65m
  • CWE Classification: CWE-269: Improper Privilege Management
  • CVSS v3.1 Score: 6.8 Medium (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N)
  • Affected Component: SilverStripe\Security\Group (canEdit and validate methods)
  • Attack Vector: Authenticated Network (Requires CMS_ACCESS_SecurityAdmin)
  • Security Impact: Privilege Escalation to Full Administrator (ADMIN)
  • Fixed Version: silverstripe/framework 6.2.13
  • Exploit / KEV Status: No known public exploits; Not listed in CISA KEV

Affected Systems

  • Silverstripe Framework (silverstripe/framework)
  • Silverstripe CMS
  • silverstripe/framework: < 6.2.13 (Fixed in: 6.2.13)

Code Analysis

Commit: bb4d04a

[CVE-2026-91112] CMS_ACCESS_SecurityAdmin privilege escalation

diff --git a/src/Security/Group.php b/src/Security/Group.php
index d0b1c5afe08..c9f01015aeb 100755
--- a/src/Security/Group.php
+++ b/src/Security/Group.php
@@ -517,11 +517,7 @@ public function validate(): ValidationResult
         if ($this->Parent()->exists() && !Permission::check('ADMIN')) {
             $privilegedCodes = Permission::config()->get('privileged_permissions');
             if (!empty($privilegedCodes)) {
-                $inheritedCodes = Permission::get()->filter([
-                    'GroupID' => $this->Parent()->collateAncestorIDs(),
-                    'Code' => $privilegedCodes,
-                ]);
-                if ($inheritedCodes->exists()) {
+                if ($this->anyGroupGrantsPermission($this->Parent()->collateAncestorIDs(), $privilegedCodes)) {
                     $result->addError(
                         _t(
                             'SilverStripe\\Security\\Group.HierarchyPermsError',
@@ -594,7 +590,7 @@ protected function onBeforeDelete()

     /**
      * Checks for permission-code CMS_ACCESS_SecurityAdmin.
-     * If the group has ADMIN permissions, it requires the user to have ADMIN permissions as well.
+     * If the group grants a permission leading to ADMIN, it requires the user to have ADMIN permissions as well.
      *
      * @param Member $member Member
      * @return boolean
@@ -614,11 +610,11 @@ public function canEdit($member = null)
         if (// either we have an ADMIN
             (bool)Permission::checkMember($member, "ADMIN")
             || (
-                // or a privileged CMS user and a group without ADMIN permissions.
+                // or a privileged CMS user and a group that does not grant a permission leading to ADMIN.
                 // without this check, a user would be able to add himself to an administrators group
                 // with just access to the "Security" admin interface
                 Permission::checkMember($member, "CMS_ACCESS_SecurityAdmin") &&
-                !Permission::get()->filter(['GroupID' => $this->ID, 'Code' => 'ADMIN'])->exists()
+                !$this->grantsEscalatingPermissions()
             )
         ) {
             return true;
@@ -627,6 +623,39 @@ public function canEdit($member = null)
         return false;
     }

+    /**
+     * Determine whether a member of this group would receive a permission that leads to ADMIN, whether granted
+     * directly, via an assigned PermissionRole, or inherited from an ancestor group. Used to stop a non-admin user
+     * with only CMS_ACCESS_SecurityAdmin from editing an admin-equivalent group and escalating their own privileges.
+     */
+    private function grantsEscalatingPermissions(): bool
+    {
+        if (!$this->exists()) {
+            return false;
+        }
+        $privilegedCodes = Permission::config()->get('privileged_permissions') ?? [];
+        // EDIT_PERMISSIONS is privileged but cannot reach ADMIN - PermissionCheckboxSetField::saveInto()
+        // strips every privileged code from a non-admin's submission
+        $escalatingCodes = array_diff($privilegedCodes, ['EDIT_PERMISSIONS']);
+        return $this->anyGroupGrantsPermission($this->collateAncestorIDs(), $escalatingCodes);
+    }
+
+    /**
+     * Determine whether any of the given groups grants any of the given permission codes to its members,
+     * whether the code is assigned to the group directly or via an assigned PermissionRole.
+     *
+     * @param int[] $groupIDs
+     * @param string|string[] $codes
+     */
+    private function anyGroupGrantsPermission(array $groupIDs, array|string $codes): bool
+    {
+        if (empty($groupIDs) || empty($codes)) {
+            return false;
+        }
+        $grantingGroupIDs = Permission::get_groups_by_permission($codes)->columnUnique('ID');
+        return !empty(array_intersect($groupIDs, $grantingGroupIDs));
+    }
+
     /**
      * Checks for permission-code CMS_ACCESS_SecurityAdmin.
      *
Enter fullscreen mode Exit fullscreen mode

Mitigation Strategies

  • Upgrade silverstripe/framework to version 6.2.13 or later to enforce ancestor and role checks during Group editing and reparenting.
  • Restrict the CMS_ACCESS_SecurityAdmin permission exclusively to full administrators until the patch is deployed.
  • Remove child groups from beneath any group that holds ADMIN privileges.
  • Assign the ADMIN permission directly to administrative groups rather than through PermissionRole objects if running an unpatched version.

Remediation Steps:

  1. Update composer dependencies by running: composer update silverstripe/framework
  2. Verify that the installed version of silverstripe/framework is 6.2.13 or higher using: composer show silverstripe/framework
  3. Audit the Group_Members, Group_Roles, and Group tables in the database to ensure no unauthorized member associations or group reparenting occurred prior to patching.

References


Read the full report for CVE-2026-91112 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)