Silverstripe Framework has a XSS vulnerability in HTML editor
Published 10 Apr 2025 · Updated 10 Apr 2025
Affected package
- Affected
- <5.3.23
- Fixed in
- 5.3.23
composer require silverstripe/framework:^5.3.23Details
Impact
A bad actor with access to edit content in the CMS could send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of the site. The payload would be sanitised on the client-side, but server-side sanitisation doesn't catch it.
The server-side sanitisation logic has been updated to sanitise against this attack.
Reported by
James Nicoll from Fujitsu Cyber
References
- https://www.silverstripe.org/download/security-releases/cve-2025-30148
Is GHSA-rhx4-hvx9-j387 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/security/advisories/GHSA-rhx4-hvx9-j387
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-30148
- Linkgithub.com/silverstripe/silverstripe-framework/pull/11682
- Linkgithub.com/silverstripe/silverstripe-framework/commit/e99cfd62d160d145a76fcf9631e6b11226e42358
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2025-30148.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/cve-2025-30148
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.