Vulnerability Database · Packagist · Package report

silverstripe/admin: vulnerability history, versions and safety

silverstripe/admin is a package in the Packagist ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Oct 2021 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded M6 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on silverstripe/admin i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 22 May 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 7 vulnerabilities on record across 2 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 7 over 2 years · 0 in the last year i
  • Latest disclosure 22 May 2024 i
  • Highest CVSS 6.1 i
  • With no published fix 0 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/admin, 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
1.13.18 M1 Yes Details →
1.13.17 M1 Yes Details →
1.13.16 M1 Yes Details →
1.13.15 M1 Yes Details →
1.13.14 M1 Yes Details →
1.13.13 M1 Yes Details →
1.13.12 M1 Yes Details →
1.13.11 M1 Yes Details →
1.13.10 M1 Yes Details →
1.13.9 M1 Yes Details →
1.13.8 M1 Yes Details →
1.13.7 M1 Yes Details →
1.13.6 M1 Yes Details →
1.13.5 M3 Yes Details →
1.13.4 M3 Yes Details →
1.13.3 M3 Yes Details →
1.13.2 M3 Yes Details →
1.13.1 M3 Yes Details →
1.13.0 M3 Yes Details →
1.13.0-rc1 M3 Yes Details →
1.13.0-beta1 M3 Yes Details →
1.12.7 M3 Yes Details →
1.12.6 M4 Yes Details →
1.12.5 M4 Yes Details →
1.12.4 M4 Yes Details →
1.12.3 M4 Yes Details →
1.12.2 M4 Yes Details →
1.12.1 M4 Yes Details →
1.12.0 M4 Yes Details →
1.12.0-rc1 M4 Yes Details →
1.12.0-beta1 M4 Yes Details →
1.11.3 M4 Yes Details →
1.11.2 M5 Yes Details →
1.11.1 M5 Yes Details →
1.11.0 M5 Yes Details →
1.11.0-rc1 M5 Yes Details →
1.11.0-beta1 M5 Yes Details →
1.10.4 M5 Yes Details →
1.10.3 M5 Yes Details →
1.10.2 M5 Yes Details →
1.10.1 M5 Yes Details →
1.10.0 M5 Yes Details →
1.10.0-rc1 M5 Yes Details →
1.10.0-beta1 M5 Yes Details →
1.9.0 M5 Yes Details →
1.9.0-rc1 M5 Yes Details →
1.9.0-beta1 M5 Yes Details →
1.9.0-alpha1 M5 Yes Details →
1.8.1 M5 Yes Details →
1.8.0 M6 Yes Details →
1.8.0-rc1 M6 Yes Details →
1.8.0-beta1 M6 Yes Details →
1.7.4 M6 Yes Details →
1.7.3 M6 Yes Details →
1.7.2 M6 Yes Details →
1.7.1 M6 Yes Details →
1.7.0 M6 Yes Details →
1.7.0-rc1 M6 Yes Details →
1.7.0-beta1 M6 Yes Details →
1.6.4 M6 Yes Details →
1.6.3 M6 Yes Details →
1.6.2 M6 Yes Details →
1.6.1 M6 Yes Details →
1.6.0 M6 Yes Details →
1.6.0-rc1 M6 Yes Details →
1.6.0-beta1 M6 Yes Details →
1.5.2 M6 Yes Details →
1.5.1 M6 Yes Details →
1.5.0 M6 Yes Details →
1.5.0-rc2 M6 Yes Details →
1.5.0-rc1 M6 Yes Details →
1.5.0-alpha1 M6 Yes Details →
1.4.5 M6 Yes Details →
1.4.4 M6 Yes Details →
1.4.3 M6 Yes Details →
1.4.2 M6 Yes Details →
1.4.1 M6 Yes Details →
1.4.0 M6 Yes Details →
1.4.0-rc1 M6 Yes Details →
1.3.5 M6 Yes Details →
1.3.4 M6 Yes Details →
1.3.3 M6 Yes Details →
1.3.2 M6 Yes Details →
1.3.1 M6 Yes Details →
1.3.0 M6 Yes Details →
1.3.0-rc1 M6 Yes Details →
1.2.6 M6 Yes Details →
1.2.5 M6 Yes Details →
1.2.4 M6 Yes Details →
1.2.3 M6 Yes Details →
1.2.2 M6 Yes Details →
1.2.1 M6 Yes Details →
1.2.0 M6 Yes Details →
1.2.0-beta1 M6 Yes Details →
1.1.5 M6 Yes Details →
1.1.4 M6 Yes Details →
1.1.3 M6 Yes Details →
1.1.2 M6 Yes Details →
1.1.1 M6 Yes Details →
1.1.0 M6 Yes Details →
1.1.0-rc2 M6 Yes Details →
1.1.0-rc1 M6 Yes Details →
1.0.7 M6 Yes Details →
1.0.6 M6 Yes Details →
1.0.5 M6 Yes Details →
1.0.4 M6 Yes Details →
1.0.3 M6 L1 Yes Details →
1.0.2 M6 Yes Details →
1.0.1 M6 Yes Details →
1.0.1-rc1 M6 Yes Details →
1.0.0 M6 Yes Details →
1.0.0-rc3 M2 Yes Details →
1.0.0-rc2 M2 Yes Details →
1.0.0-rc1 M2 Yes Details →
1.0.0-beta4 M2 Yes Details →
1.0.0-beta3 M2 Yes Details →
1.0.0-beta2 M2 Yes Details →
1.0.0-beta1 M2 Yes Details →
1.0.0-alpha7 M2 Yes Details →
1.0.0-alpha6 M2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2023 3
  • 2024 2

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

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

Is silverstripe/admin safe to use?

Vulert records 7 vulnerabilities for silverstripe/admin in Packagist: 0 critical, 0 high, 6 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does silverstripe/admin have?

7 vulnerabilities are recorded for silverstripe/admin in the Packagist ecosystem: 0 critical, 0 high, 6 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/admin vulnerabilities disclosed?

0 vulnerabilities were recorded for silverstripe/admin in the last 12 months, and the oldest entry in this database dates to 12 Oct 2021. 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/admin 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/admin for upcoming vulnerabilities?

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