VulnerabilityPublished 20 Mar 2026Updated 23 Mar 2026

CVE-2026-33177: statamic cms · Missing Authorization

Affects statamic cmsSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 6.7.0 or 5.73.14 when convenient.

Data as of 1 Nov 2026, 11:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.7.0, 5.73.14

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade cms to 6.7.0 or 5.73.14; statamic/cms to 5.73.14.

Affected software

Product	Affected	Fixed in
statamiccms	Affected >=6.0.0-alpha.1 <6.7.0	Fixed in 6.7.0
statamiccms	Affected <5.73.14	Fixed in 5.73.14
Packagiststatamic/cms`pkg:composer/statamic/cms`Other threats	Affected <5.73.14	Fixed in 5.73.14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-33177, organizations should promptly upgrade Statamic CMS to versions 5.73.14 or 6.7.0, where the authorization bypass has been fixed. Until upgrades are applied, restrict Control Panel access strictly to trusted users and review user roles and permissions to minimize low-privileged user capabilities. Implement network-level controls such as IP whitelisting or VPN access to limit exposure of the Control Panel endpoints. Monitor logs for unusual requests to the field action processing endpoint indicative of unauthorized taxonomy term creation attempts. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting this vulnerability. Conduct regular audits of taxonomy data to detect unauthorized changes. Additionally, consider implementing multi-factor authentication (MFA) for Control Panel access to reduce the risk of compromised credentials being used to exploit this vulnerability. Finally, maintain an up-to-date inventory of CMS versions in use and subscribe to vendor security advisories to stay informed about patches and emerging threats.

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.

Impact

The primary impact of CVE-2026-33177 is on the integrity of content managed by Statamic CMS. Unauthorized creation of taxonomy terms by low-privileged users can lead to unauthorized modifications of site structure, categorization, and metadata, which may affect content organization, navigation, and potentially SEO. While confidentiality and availability are not directly impacted, the integrity compromise could facilitate further attacks or misuse, such as misleading site visitors or enabling privilege escalation chains if combined with other vulnerabilities. Organizations relying on Statamic CMS for content management, especially those with multiple user roles and complex taxonomy structures, face risks of unauthorized content manipulation. This could undermine trust in the website's content and potentially cause operational disruptions if taxonomy data is critical to business processes. The vulnerability's ease of exploitation and network accessibility increase the risk, particularly in environments where low-privileged users have access to the Control Panel. However, the absence of known active exploits reduces immediate threat urgency but does not eliminate the risk of future exploitation.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/statamic/cms/security/advisories/GHSA-wh3h-gvc4-cc2g (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 22:55 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats