CVE-2023-44401: The Silverstripe CMS GraphQL Server serves Silverstripe data as GraphQL representations

Routine

MEDIUM 5.3REMOTEUPGRADE

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

The Silverstripe CMS GraphQL Server serves Silverstripe data as GraphQL representations. In versions 4.0.0 prior to 4.3.7 and 5.0.0 prior to 5.1.3, `canView` permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page. Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se. This has been fix

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-863
Published	2024-01-23
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: silverstripe

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

Am I affected?

Timeline

2024-01-23 14:15 UTCPublished CVE record published
2026-06-17 06:27 UTCUpdated Record last modified

silverstripe graphql UPGRADE

Affected: >= 4.0.0 and < 4.3.7 · >= 5.0.0 and < 5.1.3

Fixed in: 4.3.7, 5.1.3

Safe to downgrade to: a release before 4.0.0

1. Check installed version

apt-cache policy graphql || rpm -q graphql || graphql --version

2. UPGRADE to 4.3.7 (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 4.0.0 (Debian / Ubuntu)

apt-cache madison graphql sudo apt install graphql=<VERSION_BEFORE_4.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_4.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-44401?

graphql: upgrade to 4.3.7, 5.1.3. Exact commands for each OS are on this page.

Is CVE-2023-44401 being exploited?

CVE-2023-44401 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-44401 affect?

CVE-2023-44401 affects graphql. Severity is medium (CVSS 5.3). The Silverstripe CMS GraphQL Server serves Silverstripe data as GraphQL representations. In versions 4.0.0 prior to 4.3.7 and 5.0.0 prior to 5.1.3, `canView` permission checks are bypassed for ORM data in paginated GraphQL query results whe

How urgent is CVE-2023-44401?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2023-40180 HIGH 7.5 UPGRADE silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations
CVE-2023-28104 HIGH 7.5 DOWNGRADE `silverstripe/graphql` serves Silverstripe data as GraphQL representations
CVE-2023-26144 MEDIUM 5.3 UPGRADE Versions of the package graphql from 16.3.0 and before 16.8.1 are vulnerable to Denial of Service (DoS) due to

References

← Back to latest CVEs