CVE-2026-33177
Received Received - Intake
Authorization Bypass in Statamic CMS Allows Unauthorized Taxonomy Creation

Publication date: 2026-03-20

Last updated on: 2026-03-23

Assigner: GitHub, Inc.

Description
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, 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. This has been fixed in 5.73.14 and 6.7.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-20
Last Modified
2026-03-23
Generated
2026-06-16
AI Q&A
2026-03-21
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 2 associated CPEs
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
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

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.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-33177. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart