MediumGHSA-m8v7-x398-pxrf
Silverstripe XSS in CMS Edit Page
Published 23 May 2024 · Updated 28 Nov 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=3.1.18 <3.1.19
- Fixed in
- 3.1.19
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.1.19silverstripe/frameworkComposer
- Affected
- >=3.2.3 <3.2.4
- Fixed in
- 3.2.4
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.2.4silverstripe/frameworkComposer
- Affected
- >=3.3.1 <3.3.2
- Fixed in
- 3.3.2
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.3.2Details
Due to a lack of parameter sanitisation a carefully crafted URL could be used to inject arbitrary HTML into the CMS Edit page.
An attacker could create a URL and share it with a site administrator to perform an attack.
Is GHSA-m8v7-x398-pxrf 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.
References
- Linkgithub.com/silverstripe/silverstripe-framework/commit/a24c8260b1d048dc6a0836eb1be9a1ca2056e770
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-004-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkgithub.com/silverstripe/silverstripe-framework/commits/3.3.2
- Linkwww.silverstripe.org/download/security-releases/ss-2016-004
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.