Statamic CMS's unsafe method invocation via collection sorting allows data destruction
Impact
The fix for GHSA-4jjr-vmv7-wh4w was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets.
This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value.
Patches
This has been fixed in 5.73.23 and 6.20.0.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | statamic/cms | < 5.73.23, >= 6.0.0, < 6.20.0 | 5.73.23, 6.20.0 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H- Weakness (CWE)
CWE-470- Platform
- Composer
- Package
statamic/cms- Disclosed
- 26.06.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-m92m-r54r-x8r2 - CC BY 4.0
Vulnerability history: statamic/cms
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 44
- First → latest
- 03.2022 08.2026
- Without a fix
- 1
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 15
- Medium 25
- Low 3
Disclosures per year
- 2022: 2
- 2023: 4
- 2024: 3
- 2025: 1
- 2026: 34
-
Statamic CMS's unsafe method invocation via collection sorting allows data destruction this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.