MediumGHSA-xpff-c35g-j3cr

silverstripe/framework Privilege Escalation Risk in Member Edit form

Published 27 May 2024 · Updated 2 Dec 2024

Affected packages

silverstripe/frameworkComposer
Affected
>=3.5.7-rc1 <3.5.8
Fixed in
3.5.8
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.5.8
silverstripe/frameworkComposer
Affected
>=3.6.0-rc1 <3.6.6
Fixed in
3.6.6
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.6.6
silverstripe/frameworkComposer
Affected
>=4.0.0-rc1 <4.0.4
Fixed in
4.0.4
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.0.4
silverstripe/frameworkComposer
Affected
>=4.1.0-rc1 <4.1.1
Fixed in
4.1.1
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.1.1

Details

A member with the permission EDIT_PERMISSIONS and access to the "Security" section is able to re-assign themselves (or another member) to ADMIN level.

CMS Fields for the member are constructed using DirectGroups instead of Groups relation which results in bypassing security logic preventing privilege escalation.

Is GHSA-xpff-c35g-j3cr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.