CVE intelligence and bounded remediation

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

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 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.

Severity
Medium
CVSS
5.3 (3.1)
Published
2024-01-23
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-863

Affected products

  • silverstripe / graphql

Showing 1 representative product identities from 2 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Authorization bypass, IDOR, and cross-tenant access

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map object and action authorization checks across API, UI, batch, import/export, and background-job paths.
  • Identify tenant, ownership, role, and policy boundaries for affected resources and administrative operations.
  • Use synthetic fixtures to compare intended access matrices without accessing another user's real data.

Remediate safely

  • Enforce server-side authorization at each resource access and state transition using the authenticated principal and trusted tenant context.
  • Scope data queries by tenant and ownership; treat client-supplied identifiers, roles, and policy claims as untrusted.
  • Add deny-by-default policy tests for horizontal and vertical access across every affected transport.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.