CVE-2023-44401 — graphql
MEDIUMCVE-2023-44401 is a medium-severity (CVSS 5.3) CWE-863 vulnerability in silverstripe/graphql. A fix is available for silverstripe/graphql — see the affected versions and patch details below.
Silverstripe GraqhQL's view permissions are bypassed for paginated lists of ORM data
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-44401.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
silverstripe/graphql🐘silverstripe/graphqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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 fixed by ensuring no new records are pulled in from the database after performing canView permission checks for each page of results. This may result in some pages in your query results having less than the maximum number of records per page even when there are more pages of results.
This behaviour is consistent with how pagination works in other areas of Silverstripe CMS, such as in GridField, and is a result of having to perform permission checks in PHP rather than in the database directly.
You can choose to disable these permission checks by disabling the CanViewPermission plugin following the instructions in overriding default plugins.
Note that this vulnerability does not affect version 3.x.
Base CVSS: 5.3 Reported by: Eduard Briem from Hothouse Creative, Nelson
References
https://www.silverstripe.org/download/security-releases/CVE-2023-44401
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/graphql | ≥ 4.0.0&&< 4.3.7 | 4.3.7composer require silverstripe/graphql:^4.3.7 |
| 🐘Packagist | silverstripe/graphql | ≥ 5.0.0&&< 5.1.3 | 5.1.3composer require silverstripe/graphql:^5.1.3 |
Affected Products
graphqlsilverstripeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/graphql to 4.3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-44401 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2023-44401 in your dependencies?
Find it across Packagist, including transitive dependencies.