Silverstripe XSS In rewritten hash links
Published 23 May 2024 · Updated 28 Nov 2024
Affected packages
- Affected
- <3.0.13
- Fixed in
- 3.0.13
composer require silverstripe/framework:^3.0.13- Affected
- >=3.1.0 <3.1.12
- Fixed in
- 3.1.12
composer require silverstripe/framework:^3.1.12Details
A high level XSS vulnerability has been discovered in the SilverStripe framework which causes links containing hash anchors (E.g. href="#anchor") to be rewritten in an unsafe way.
The rewriteHashlinks option on SSViewer will rewrite these to contain the current url, although without adequate escaping, meaning that HTML could be injected via injecting unsafe values to any page via the querystring.
Due to the nature of this issue it is likely that a large number of SilverStripe sites are affected.
Is GHSA-34q6-xqxh-gq39 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/604c32871202064a4aa12c3b3fd58140231685e5
- Linkgithub.com/silverstripe/silverstripe-framework/commit/bdef4fc7a548c7c243ff86f2db7c16f301a6f120
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2015-009-1.yaml
- Linkwww.silverstripe.org/software/download/security-releases/ss-2015-009-xss-in-rewritten-hash-links
- Packagesilverstripe/silverstripe-framework
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.