Is silverstripe/subsites 2.6 vulnerable?
Composer · 2 releases from 2.6.0 to 2.6.1 · latest silverstripe/subsites is 4.0.1 · checked 18 Nov 2026
No known advisories in the last release
silverstripe/subsites 2.6.1, the last 2.6 release, has no known advisories. 1 advisory affects earlier 2.6.x releases, so update to 2.6.1.
composer require silverstripe/subsites:^2.6.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
Fixed within 2.6.x, affecting earlier releases
SilverStripe Subsite weakens file permissions
- Affected
- >=2.0.0 <2.6.1
- Fixed in
- 2.6.1
Every silverstripe/subsites 2.6.x release
Affected: 2.6.0. 2.6.1 is not affected. Latest silverstripe/subsites: 4.0.1.
| Version | Known advisories |
|---|---|
| silverstripe/subsites 2.6.1 | None |
| silverstripe/subsites 2.6.0 | CVE-2022-42949 |
Which of your client projects are still on silverstripe/subsites 2.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact silverstripe/subsites version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other silverstripe/subsites versions
- silverstripe/subsites 3.0
- silverstripe/subsites 2.8
- silverstripe/subsites 2.7
- silverstripe/subsites 2.5
- silverstripe/subsites 2.4
- silverstripe/subsites 2.3
- silverstripe/subsites 4.0
- silverstripe/subsites 3.4
- silverstripe/subsites 3.3
- silverstripe/subsites 3.2
- silverstripe/subsites 3.1
- All silverstripe/subsites advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.