silverstripe/cms vulnerabilities
The SilverStripe Content Management System
- Registry
- Composer
- Latest
- 6.2.5
- License
- BSD-3-Clause
16 known advisories
The latest version, 6.2.5, is not affected by any of them. Projects on older versions may be.
composer require silverstripe/cms:^6.2.5Security advisories for silverstripe/cms
Silverstripe: XSS in breadcrumbs in page list view
- Affected
- <6.2.1
- Fixed in
- 6.2.1
Silverstripe SiteTree Creation Permission Vulnerability
- Affected
- >=3.0.0 <3.0.12 · >=3.1.0 <3.1.11
- Fixed in
- 3.0.12, 3.1.11
Silverstripe XSS vulnerability via VirtualPage
- Affected
- >=3.1.0 <3.1.10
- Fixed in
- 3.1.10
Silverstripe History XSS Vulnerability
- Affected
- >=3.1.0 <3.1.10
- Fixed in
- 3.1.10
Silverstipe CMS Stored XSS in custom meta tags
- Affected
- >=4.0.0 <4.11.3
- Fixed in
- 4.11.3
Silverstripe CMS malicious file upload enables script execution
- Affected
- <=4.5.0
- Fixed in
- No fix released
Silverstripe CMS XSS Vulnerability
- Affected
- <=4.5.0
- Fixed in
- No fix released
Silverstripe CMS information disclosure
- Affected
- <=4.5.0
- Fixed in
- No fix released
Silverstripe CMS Arbitrary Code Execution
- Affected
- >=2.4.0 <2.4.6
- Fixed in
- 2.4.6
Silverstripe CMS XSS Vulnerability
- Affected
- <3.6.1
- Fixed in
- 3.6.1
Silverstripe CMS User Enumeration
- Affected
- <3.5.5 · >=3.6 <3.6.1
- Fixed in
- 3.5.5, 3.6.1
Silverstripe CMS Open Redirect
- Affected
- <=3.1.13
- Fixed in
- No fix released
SilverStripe vulnerable to Cross-site Scripting
- Affected
- <2.3.5
- Fixed in
- 2.3.5
Silverstripe CMS XSS Vulnerability
- Affected
- <3.4.4 · >=3.5.0 <3.5.2
- Fixed in
- 3.4.4, 3.5.2
Silverstripe CMS XSS Vulnerability
- Affected
- <3.1.16 · >=3.2.0 <3.2.1
- Fixed in
- 3.1.16, 3.2.1
Missing warning can lead to unauthenticated admin access in SilverStripe
- Affected
- >=4.4.0 <4.4.4
- Fixed in
- 4.4.4
Which of your client projects still run an old silverstripe/cms?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.