CVE-2023-44401
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 fixed in versions 4.3.7 and 5.1.3 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 the query results having less than the maximum number of records per page even when there are more pages of results. This behavior 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. One may disable these permission checks by disabling the `CanViewPermission` plugin.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn affected versions of Silverstripe CMS GraphQL Server (4.0.0-4.3.6 and 5.0.0-5.1.2), the canView permission checks are bypassed for paginated GraphQL query results when the total number of records exceeds the page size. This occurs because the permission checks are not reapplied after the first page of results is retrieved, allowing unauthorized access to records that should be protected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0.0, < 4.3.7>= 5.0.0, < 5.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed GraphQL module versionRun 'composer show silverstripe/graphql' or check your composer.lock file for the silverstripe/graphql version numberAffected if The version is >= 4.0.0 and < 4.3.7, or >= 5.0.0 and < 5.1.3
-
Verify the GraphQL module is enabledLook for the silverstripe/graphql module in your project's vendor directory or check _config.php for GraphQL configurationAffected if The GraphQL module is installed and active in the Silverstripe CMS installation
-
Confirm the CanViewPermission plugin is in useInspect your GraphQL schema configuration files for 'CanViewPermission' plugin registration or check _config/graphql.yml for permission plugin settingsAffected if The CanViewPermission plugin is enabled in your GraphQL schema configuration
-
Identify paginated GraphQL queries using canViewSearch your GraphQL query definitions for paginated query types (e.g., offset-based or cursor-based pagination) that interact with DataObjects protected by canView permissionsAffected if Your application uses paginated GraphQL queries against DataObjects with canView permission controls
Your environment is affected if you have a Silverstripe GraphQL version in the vulnerable range AND the CanViewPermission plugin is enabled AND you use paginated queries against protected DataObjects where the total record count can exceed the page size.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.3.75.1.3
Upgrade to Silverstripe CMS GraphQL Server version 4.3.7 or 5.1.3, or alternatively disable the CanViewPermission plugin if permission enforcement is not required.
Upgrade to silverstripe/graphql version 4.3.7 (for v4) or 5.1.3 (for v5)
- Identify the current GraphQL module version in your Silverstripe CMS project by checking your composer.json or vendor directory
- For Silverstripe CMS 4.x users: Run `composer require silverstripe/graphql:^4.3.7` to upgrade to the fixed version
- For Silverstripe CMS 5.x users: Run `composer require silverstripe/graphql:^5.1.3` to upgrade to the fixed version
- Run `composer update silverstripe/graphql` to apply the changes
- Clear your Silverstripe cache by running `php vendor/bin/flush` or `?flush=1` on your site
- Test your GraphQL queries to verify permission checks are now enforced correctly, noting that some paginated results may return fewer records per page than before
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-44401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data