CVE-2026-33177
Authorization Bypass in Statamic CMS Allows Unauthorized Taxonomy Creation
Publication date: 2026-03-20
Last updated on: 2026-03-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| statamic | statamic | to 5.73.14 (exc) |
| statamic | statamic | From 6.0.0 (inc) to 6.7.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Statamic, a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, low-privileged Control Panel users were able to create taxonomy terms by submitting requests to the field action processing endpoint with attacker-controlled field definitions. This allowed them to bypass the authorization checks that are normally enforced on the standard taxonomy term creation endpoint.
The issue was fixed in versions 5.73.14 and 6.7.0.
How can this vulnerability impact me? :
This vulnerability allows low-privileged users to bypass authorization controls and create taxonomy terms that they should not be able to create. This could lead to unauthorized modification or addition of content taxonomy within the CMS.
While the CVSS score indicates no impact on confidentiality or availability, there is a low impact on integrity, meaning that unauthorized changes to data could occur.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Statamic to version 5.73.14 or later, or version 6.7.0 or later, where the issue has been fixed.