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

Advisory record · `GHSA-m92m-r54r-x8r2`

- **Identifiers:** `GHSA-m92m-r54r-x8r2` · `CVE-2026-49287` · `PKSA-fhw5-pm86-31ff`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-470](https://cwe.mitre.org/data/definitions/470.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 26 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Jun 2026, 22:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `statamic/cms` (Packagist): affected `<5.73.23 || >=6.0.0, <6.20.0`; fixed in `5.73.23`, `6.20.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Statamic CMS (Packagist statamic/cms) versions before 5.73.23 and from 6.0.0 before 6.20.0 are affected. The source says an incomplete earlier fix left in-memory collection sorting unprotected, so manipulated sort parameters can lead to loss of content and assets, but only when a front-end template passes request input into a tag's sort parameter, which is not the default setup. Upgrade to 5.73.23 or 6.20.0.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:57 UTC: First seen by agentprime
- 31 Oct 2026, 13:57 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m92m-r54r-x8r2)

## Sources

- [GitHub Advisory Database: GHSA-m92m-r54r-x8r2](https://github.com/advisories/GHSA-m92m-r54r-x8r2)
- [OSV: GHSA-m92m-r54r-x8r2](https://osv.dev/vulnerability/GHSA-m92m-r54r-x8r2)
- <https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w>
- <https://github.com/statamic/cms/security/advisories/GHSA-m92m-r54r-x8r2>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-49287>
- <https://github.com/statamic/cms>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m92m-r54r-x8r2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m92m-r54r-x8r2/>. Everything for agents: <https://agentprime.io/llms.txt>.