Vulnerability Database · Packagist · Package report

silverstripe/graphql: vulnerability history, versions and safety

silverstripe/graphql is a package in the Packagist ecosystem. Vulert records 7 vulnerabilities for it across 70 releases, from Jun 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 H4 M3
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/graphql i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 28 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 28 May 2024 i
  • Highest CVSS 8.8 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/graphql, 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
4.3.6 M1 Yes Details →
4.3.5 M1 Yes Details →
4.3.4 M1 Yes Details →
4.3.3 M1 Yes Details →
4.3.2 M1 Yes Details →
4.3.1 M1 Yes Details →
4.3.0 M1 Yes Details →
4.3.0-rc1 M1 Yes Details →
4.2.5 M1 Yes Details →
4.2.4 M1 Yes Details →
4.2.3 M1 Yes Details →
4.2.2 M1 Yes Details →
4.2.1 M1 Yes Details →
4.2.0 M1 Yes Details →
4.1.3 M1 Yes Details →
4.1.2 M1 Yes Details →
4.1.1 H1 M1 Yes Details →
4.1.0 M1 Yes Details →
4.1.0-rc1 M1 Yes Details →
4.1.0-beta1 M1 Yes Details →
4.0.2 M1 Yes Details →
4.0.1 M1 Yes Details →
4.0.0 M1 Yes Details →
3.8.1 H1 Yes Details →
3.8.0 H1 Yes Details →
3.7.2 H1 Yes Details →
3.7.1 H1 Yes Details →
3.7.0 H1 Yes Details →
3.6.0 H1 Yes Details →
3.6.0-rc1 H1 Yes Details →
3.6.0-beta1 H1 Yes Details →
3.6.0-alpha2 H1 Yes Details →
3.6.0-alpha1 H1 Yes Details →
3.5.2 H1 Yes Details →
3.5.1 H1 M1 Yes Details →
3.5.0 H1 M1 Yes Details →
3.5.0-rc1 H1 M2 Yes Details →
3.5.0-beta1 H1 M2 Yes Details →
3.4.1 H1 M2 Yes Details →
3.4.0 H1 M2 Yes Details →
3.4.0-rc1 H1 M2 Yes Details →
3.4.0-beta1 H1 M2 Yes Details →
3.3.0 H1 M2 Yes Details →
3.3.0-rc1 H1 M2 Yes Details →
3.3.0-beta1 H1 M2 Yes Details →
3.2.4 H1 M2 Yes Details →
3.2.3 H1 M2 Yes Details →
3.2.2 H1 M2 Yes Details →
3.2.1 H1 M2 Yes Details →
3.2.0 H1 M2 Yes Details →
3.2.0-rc2 H1 M2 Yes Details →
3.2.0-rc1 H1 M2 Yes Details →
3.2.0-alpha1 H1 M2 Yes Details →
3.1.5 H1 M2 Yes Details →
3.1.4 H1 M2 Yes Details →
3.1.3 H1 M2 Yes Details →
3.1.2 H1 M2 Yes Details →
3.1.1 H1 M2 Yes Details →
3.1.0 H1 M2 Yes Details →
3.1.0-rc1 H1 M2 Yes Details →
3.0.4 H1 M2 Yes Details →
3.0.3 H1 M2 Yes Details →
3.0.2 H1 M2 Yes Details →
3.0.1 H1 M2 Yes Details →
3.0.0 H1 M2 Yes Details →
2.0.4 H1 Yes Details →
2.0.3 H1 Yes Details →
2.0.2 H2 Yes Details →
2.0.1 H2 Yes Details →
2.0.0 H2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 1
  • 2023 2
  • 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.

03 Vulnerabilities

Recorded vulnerabilities for silverstripe/graphql

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 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/graphql

Is silverstripe/graphql safe to use?

Vulert records 7 vulnerabilities for silverstripe/graphql in Packagist: 0 critical, 4 high, 3 medium and 0 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/graphql have?

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

How often are new silverstripe/graphql vulnerabilities disclosed?

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

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