silverstripe/subsites vulnerabilities
Run multiple sites from a single SilverStripe install.
- Registry
- Composer
- Latest
- 4.0.1
- License
- BSD-3-Clause
2 known advisories
The latest version, 4.0.1, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require silverstripe/subsites:^4.0.1Is your project on an affected silverstripe/subsites?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for silverstripe/subsites
silverstripe/subsites Unsafe SQL Query Construction (Safe Data Source)
- Affected
- >=2.0.0 <2.1.1
- Fixed in
- 2.1.1
SilverStripe Subsite weakens file permissions
- Affected
- >=2.0.0 <2.6.1
- Fixed in
- 2.6.1
Is your silverstripe/subsites version vulnerable?
- silverstripe/subsites 4.0No known advisories in 4.0.1
- silverstripe/subsites 3.4No known advisories in 3.4.5
- silverstripe/subsites 3.3No known advisories in 3.3.1
- silverstripe/subsites 3.2No known advisories in 3.2.4
- silverstripe/subsites 3.1No known advisories in 3.1.2
- silverstripe/subsites 3.0No known advisories in 3.0.3
- silverstripe/subsites 2.8No known advisories in 2.8.7
- silverstripe/subsites 2.7No known advisories in 2.7.0
- silverstripe/subsites 2.6No known advisories in 2.6.1
- silverstripe/subsites 2.51 advisory in 2.5.0
- silverstripe/subsites 2.41 advisory in 2.4.1
- silverstripe/subsites 2.31 advisory in 2.3.3
Which of your client projects still run an old silverstripe/subsites?
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.