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

Is your project on an affected silverstripe/subsites?

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/subsites

  • HighGHSA-xc69-p8fc-m6m528 May 2024

    silverstripe/subsites Unsafe SQL Query Construction (Safe Data Source)

    Affected
    >=2.0.0 <2.1.1
    Fixed in
    2.1.1
  • MediumCVE-2022-42949GHSA-cx45-565q-6qx819 Dec 2022

    SilverStripe Subsite weakens file permissions

    Affected
    >=2.0.0 <2.6.1
    Fixed in
    2.6.1

Is your silverstripe/subsites version vulnerable?

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.