Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-40180: silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations

48
This month
HIGH 7.5REMOTEUPGRADE

CVE-2023-40180 is a high-severity flaw (CVSS 7.5) affecting graphql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations. 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 hoste

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-400
Published2023-10-16
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: silverstripe

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

silverstripe graphql UPGRADE
Affected: >= 3.0.0 and < 3.8.2 · >= 4.0.0 and < 4.1.3 · >= 4.2.0 and < 4.2.5 · >= 4.3.0 and < 4.3.4 · >= 5.0.0 and < 5.0.3
Fixed in: 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy graphql || rpm -q graphql || graphql --version
2. UPGRADE to 3.8.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade graphql
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade graphql
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison graphql sudo apt install graphql=<VERSION_BEFORE_3.0.0> sudo apt-mark hold graphql
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list graphql sudo dnf downgrade graphql-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add graphql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-40180?

graphql: upgrade to 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3. Exact commands for each OS are on this page.

Is CVE-2023-40180 being exploited?

CVE-2023-40180 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-40180 affect?

CVE-2023-40180 affects graphql. Severity is high (CVSS 7.5). silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations. An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly aff

How urgent is CVE-2023-40180?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.