silverstripe/assets vulnerabilities
SilverStripe Assets component
- Registry
- Composer
- Latest
- 3.2.2
- License
- BSD-3-Clause
6 known advisories
The latest version, 3.2.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require silverstripe/assets:^3.2.2Security advisories for silverstripe/assets
Silverstripe Assets Module has a DBFile::getURL() permission bypass
- Affected
- <2.4.5 · >=3.0.0 <3.1.3
- Fixed in
- 2.4.5, 3.1.3
Silverstripe XSS in shortcodes
- Affected
- >=1.0.0 <1.11.1
- Fixed in
- 1.11.1
XSS via uploaded gpx file
- Affected
- >=1.0.0 <1.11.1
- Fixed in
- 1.11.1
Unpublished, protected files can be published via shortcode
- Affected
- >=1.0.0 <1.10.1
- Fixed in
- 1.10.1
SilverStripe Folders migrated from 3.x may be unsafe to upload to
- Affected
- >=1.0.0 <1.4.7 · >=1.5.0 <1.5.2
- Fixed in
- 1.4.7, 1.5.2
Lack of access control on upoaded files
- Affected
- >=1.0.0 <1.3.5 · >=1.4.0 <1.4.4
- Fixed in
- 1.3.5, 1.4.4
Which of your client projects still run an old silverstripe/assets?
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.