MediumGHSA-wh3h-gvc4-cc2gCVE-2026-33177
Statamic is missing authorization check on taxonomy term creation via fieldtype
Published 18 Mar 2026 · Updated 25 Mar 2026
Affected packages
statamic/cmsComposer
- Affected
- >=6.0.0-alpha.1 <6.7.0
- Fixed in
- 6.7.0
Update to the fixed version for your release line, for example:
composer require statamic/cms:^6.7.0statamic/cmsComposer
- Affected
- <5.73.14
- Fixed in
- 5.73.14
Update to the fixed version for your release line, for example:
composer require statamic/cms:^5.73.14Details
Impact
Low-privileged Control Panel users could create taxonomy terms by submitting requests to the field action processing endpoint with attacker-controlled field definitions. This bypasses the authorization checks enforced on the standard taxonomy term creation endpoint.
Patches
This has been fixed in 5.73.14 and 6.7.0.
Is GHSA-wh3h-gvc4-cc2g 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.