Statamic: Unsafe method invocation via query value resolution allows data destruction
Published 16 Apr 2026 · Updated 8 Jul 2026
Affected packages
- Affected
- <5.73.20
- Fixed in
- 5.73.20
composer require statamic/cms:^5.73.20- Affected
- >=6.0.0-alpha.1 <6.13.0
- Fixed in
- 6.13.0
composer require statamic/cms:^6.13.0Details
Impact
Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts.
The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc.
The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too.
Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority.
Patches
This has been fixed in 5.73.20 and 6.13.0.
Is GHSA-4jjr-vmv7-wh4w 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.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.