silverstripe/admin vulnerabilities
SilverStripe admin interface
- Registry
- Composer
- Latest
- 3.2.7
- License
- BSD-3-Clause
8 known advisories
The latest version, 3.2.7, is not affected by any of them. Projects on older versions may be.
composer require silverstripe/admin:^3.2.7Security advisories for silverstripe/admin
Silverstripe admin XSS Vulnerability via WYSIWYG editor
- Affected
- >=1.0.3 <1.0.4 · >=1.1.0 <1.1.1
- Fixed in
- 1.0.4, 1.1.1
No permission checks for editing/deleting records with CSV import form
- Affected
- >=1.0.0 <1.13.19 · >=2.0.0 <2.1.8
- Fixed in
- 1.13.19, 2.1.8
SilverStripe CMS Cross-site Scripting vulnerabilities inherited from TinyMCE
- Affected
- >=1.0.0 <1.13.6
- Fixed in
- 1.13.6
Silverstripe has Cross-site Scripting (XSS) vulnerabilities inherited from TinyMCE
- Affected
- <1.13.6
- Fixed in
- 1.13.6
Cross-site scripting vulnerabilities in old version of bundled TinyMCE
- Affected
- <1.12.7
- Fixed in
- 1.12.7
URL XSS vulnerability due to outdated jquery in CMS
- Affected
- >=1.0.0 <1.11.3
- Fixed in
- 1.11.3
Silverstripe Flash Clipboard Reflected XSS
- Affected
- <1.3.5
- Fixed in
- 1.3.5
Cross-site Scripting in SilverStripe Framework
- Affected
- >=1.0.0 <1.8.1
- Fixed in
- 1.8.1
Which of your client projects still run an old silverstripe/admin?
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.