HighGHSA-m92m-r54r-x8r2CVE-2026-49287

Statamic CMS's unsafe method invocation via collection sorting allows data destruction

Published 26 Jun 2026 · Updated 10 Sept 2026

Affected packages

statamic/cmsComposer
Affected
<5.73.23
Fixed in
5.73.23
Update to the fixed version for your release line, for example:composer require statamic/cms:^5.73.23
statamic/cmsComposer
Affected
>=6.0.0 <6.20.0
Fixed in
6.20.0
Update to the fixed version for your release line, for example:composer require statamic/cms:^6.20.0

Details

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.

Is GHSA-m92m-r54r-x8r2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected statamic/cms, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.