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.0

Is your project on an affected silverstripe/recipe-cms?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • MediumCVE-2020-6165GHSA-589q-75r3-mfq424 May 2022

    Silverstripe has Incorrect Default Permissions

    Affected
    >=4.5.0 <4.5.3
    Fixed in
    4.5.3

Is your silverstripe/recipe-cms version vulnerable?

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.