silverstripe/recipe-cms vulnerabilities
SilverStripe recipe for fully featured page and asset content editing
- Registry
- Composer
- Latest
- 6.3.0
- License
- BSD-3-Clause
1 known advisory
The latest version, 6.3.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require silverstripe/recipe-cms:^6.3.0Is your project on an affected silverstripe/recipe-cms?
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/recipe-cms
Silverstripe has Incorrect Default Permissions
- Affected
- >=4.5.0 <4.5.3
- Fixed in
- 4.5.3
Is your silverstripe/recipe-cms version vulnerable?
- silverstripe/recipe-cms 6.3No known advisories in 6.3.0
- silverstripe/recipe-cms 6.2No known advisories in 6.2.0
- silverstripe/recipe-cms 6.1No known advisories in 6.1.0
- silverstripe/recipe-cms 6.0No known advisories in 6.0.0
- silverstripe/recipe-cms 5.4No known advisories in 5.4.0
- silverstripe/recipe-cms 5.3No known advisories in 5.3.0
- silverstripe/recipe-cms 5.2No known advisories in 5.2.0
- silverstripe/recipe-cms 5.1No known advisories in 5.1.0
- silverstripe/recipe-cms 5.0No known advisories in 5.0.0
- silverstripe/recipe-cms 4.13No known advisories in 4.13.0
- silverstripe/recipe-cms 4.12No known advisories in 4.12.0
- silverstripe/recipe-cms 4.11No known advisories in 4.11.1
- silverstripe/recipe-cms 4.10No known advisories in 4.10.0
- silverstripe/recipe-cms 4.9No known advisories in 4.9.0
- silverstripe/recipe-cms 4.8No known advisories in 4.8.0
Which of your client projects still run an old silverstripe/recipe-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.