Vulnerability Database · Packagist · Package report

silverstripe/cms: vulnerability history, versions and safety

silverstripe/cms is a package in the Packagist ecosystem. Vulert records 16 vulnerabilities for it across 120 releases, from Nov 2019 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded C1 H3 M11 L1
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 06 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on silverstripe/cms i

Updated on 23 Oct 2026

Careful: 4 of the 16 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 6 years, 1 in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 6 years · 1 in the last year i
  • Latest disclosure 06 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for silverstripe/cms, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
6.2.0 M1 Yes Details →
6.2.0-rc1 M1 Yes Details →
6.2.0-beta1 M1 Yes Details →
6.1.7 M1 Yes Details →
6.1.6 M1 Yes Details →
6.1.5 M1 Yes Details →
6.1.4 M1 Yes Details →
6.1.3 M1 Yes Details →
6.1.2 M1 Yes Details →
6.1.1 M1 Yes Details →
6.1.0 M1 Yes Details →
6.1.0-rc1 M1 Yes Details →
6.1.0-beta1 M1 Yes Details →
6.0.4 M1 Yes Details →
6.0.3 M1 Yes Details →
6.0.2 M1 Yes Details →
6.0.1 M1 Yes Details →
6.0.0 M1 Yes Details →
6.0.0-rc1 M1 Yes Details →
6.0.0-beta1 M1 Yes Details →
6.0.0-alpha1 M1 Yes Details →
5.4.11 M1 Yes Details →
5.4.10 M1 Yes Details →
5.4.9 M1 Yes Details →
5.4.8 M1 Yes Details →
5.4.7 M1 Yes Details →
5.4.6 M1 Yes Details →
5.4.5 M1 Yes Details →
5.4.4 M1 Yes Details →
5.4.3 M1 Yes Details →
5.4.2 M1 Yes Details →
5.4.1 M1 Yes Details →
5.4.0 M1 Yes Details →
5.4.0-rc1 M1 Yes Details →
5.4.0-beta1 M1 Yes Details →
5.3.3 M1 Yes Details →
5.3.2 M1 Yes Details →
5.3.1 M1 Yes Details →
5.3.0 M1 Yes Details →
5.3.0-rc1 M1 Yes Details →
5.3.0-beta1 M1 Yes Details →
5.2.5 M1 Yes Details →
5.2.4 M1 Yes Details →
5.2.3 M1 Yes Details →
5.2.2 M1 Yes Details →
5.2.1 M1 Yes Details →
5.2.0 M1 Yes Details →
5.2.0-rc1 M1 Yes Details →
5.2.0-beta1 M1 Yes Details →
5.1.6 M1 Yes Details →
5.1.5 M1 Yes Details →
5.1.4 M1 Yes Details →
5.1.3 M1 Yes Details →
5.1.2 M1 Yes Details →
5.1.1 M1 Yes Details →
5.1.0 M1 Yes Details →
5.1.0-rc1 M1 Yes Details →
5.1.0-beta1 M1 Yes Details →
5.0.7 M1 Yes Details →
5.0.6 M1 Yes Details →
5.0.5 M1 Yes Details →
5.0.4 M1 Yes Details →
5.0.3 M1 Yes Details →
5.0.2 M1 Yes Details →
5.0.1 M1 Yes Details →
5.0.0 M1 Yes Details →
5.0.0-rc1 M1 Yes Details →
5.0.0-beta2 M1 Yes Details →
5.0.0-beta1 M1 Yes Details →
5.0.0-alpha1 M1 Yes Details →
4.13.13 M1 Yes Details →
4.13.12 M1 Yes Details →
4.13.11 M1 Yes Details →
4.13.10 M1 Yes Details →
4.13.9 M1 Yes Details →
4.13.8 M1 Yes Details →
4.13.7 M1 Yes Details →
4.13.6 M1 Yes Details →
4.13.5 M1 Yes Details →
4.13.4 M1 Yes Details →
4.13.3 M1 Yes Details →
4.13.2 M1 Yes Details →
4.13.1 M1 Yes Details →
4.13.0 M1 Yes Details →
4.13.0-rc1 M1 Yes Details →
4.13.0-beta1 M1 Yes Details →
4.12.2 M1 Yes Details →
4.12.1 M1 Yes Details →
4.12.0 M1 Yes Details →
4.12.0-rc1 M1 Yes Details →
4.12.0-beta1 M1 Yes Details →
4.11.3 M1 Yes Details →
4.11.2 M2 Yes Details →
4.11.1 M2 Yes Details →
4.11.0 M2 Yes Details →
4.11.0-rc1 M2 Yes Details →
4.11.0-beta1 M2 Yes Details →
4.10.2 M2 Yes Details →
4.10.1 M2 Yes Details →
4.10.0 M2 Yes Details →
4.10.0-rc1 M2 Yes Details →
4.10.0-beta1 M2 Yes Details →
4.9.2 M2 Yes Details →
4.9.1 M2 Yes Details →
4.9.0 M2 Yes Details →
4.9.0-rc1 M2 Yes Details →
4.9.0-beta1 M2 Yes Details →
4.9.0-alpha1 M2 Yes Details →
4.8.0 M2 Yes Details →
4.8.0-rc1 M2 Yes Details →
4.8.0-beta2 M2 Yes Details →
4.8.0-beta1 M2 Yes Details →
4.7.2 M2 Yes Details →
4.7.1 M2 Yes Details →
4.7.0 M2 Yes Details →
4.7.0-rc1 M2 Yes Details →
4.7.0-beta1 M2 Yes Details →
4.6.0 M2 Yes Details →
4.6.0-rc1 M2 Yes Details →
4.6.0-beta1 M2 Yes Details →

Newest 120 of 348 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 11
  • 2024 3
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 16 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for silverstripe/cms

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About silverstripe/cms

Is silverstripe/cms safe to use?

Vulert records 16 vulnerabilities for silverstripe/cms in Packagist: 1 critical, 3 high, 11 medium and 1 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does silverstripe/cms have?

16 vulnerabilities are recorded for silverstripe/cms in the Packagist ecosystem: 1 critical, 3 high, 11 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new silverstripe/cms vulnerabilities disclosed?

1 vulnerability was recorded for silverstripe/cms in the last 12 months, and the oldest entry in this database dates to 12 Nov 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of silverstripe/cms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor silverstripe/cms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the silverstripe/cms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.