View permissions are bypassed for paginated lists of ORM data
Published Jan 23, 2024 · Updated Oct 23, 2026 · Also known as GHSA-jgph-w8rh-xf5p
Original summary
Normalized public record · Updated Oct 23, 2026
View permissions are bypassed for paginated lists of ORM data
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
`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.
Potential 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
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-jgph-w8rh-xf5p
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Jan 23, 2024 · Last refreshed Oct 23, 2026