HighGHSA-v23w-pppm-jh66CVE-2023-40180

Silverstripe GraphQL has DDOS Vulnerability due to lack of protection against recursive queries

Published 17 Oct 2023 · Updated 10 Sept 2026

Is your project on an affected silverstripe/graphql?

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

Affected packages

Affected
>=3.0.0 <3.8.2
Fixed in
3.8.2
Update to the fixed version for your release line, for example:composer require silverstripe/graphql:^3.8.2
Affected
>=4.0.0 <4.1.3
Fixed in
4.1.3
Update to the fixed version for your release line, for example:composer require silverstripe/graphql:^4.1.3
Affected
>=4.2.0 <4.2.5
Fixed in
4.2.5
Update to the fixed version for your release line, for example:composer require silverstripe/graphql:^4.2.5
Affected
>=4.3.0 <4.3.4
Fixed in
4.3.4
Update to the fixed version for your release line, for example:composer require silverstripe/graphql:^4.3.4
Affected
>=5.0.0 <5.0.3
Fixed in
5.0.3
Update to the fixed version for your release line, for example:composer require silverstripe/graphql:^5.0.3

Details

Impact

An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas.

If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behind a content delivery network (CDN), such as Imperva or CloudFlare, this may further mitigate the risk.

The fix includes some new configuration options which you might want to tweak for your project, based on your own requirements. See the documentation in the references for details.

Patches

Patched in 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

References

Reported by

Jason Nguyen from phew (https://phew.co.nz/)

Is GHSA-v23w-pppm-jh66 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/graphql, and gives you the command that fixes it.

More advisories for silverstripe/graphql

  • HighGHSA-wjg9-v8cf-f5q2silverstripe/graphql Cross-Site Request Forgery vulnerability · 28 May 2024
  • MediumCVE-2023-44401View permissions are bypassed for paginated lists of ORM data · 23 Jan 2024
  • HighCVE-2023-28104DDOS attack on graphql endpoints · 16 Mar 2023
  • MediumCVE-2020-6165Silverstripe has Incorrect Default Permissions · 24 May 2022
  • HighCVE-2019-12437Silverstripe CSRF Protection Bypass via GraphQL · 24 May 2022
  • MediumCVE-2021-28661SilverStripe GraphQL Server permission checker not inherited by query subclass. · 12 Oct 2021
All 8 advisories for silverstripe/graphql

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.