CVE-2026-27939
Privilege Escalation in Statmatic CMS Control Panel Authentication
Publication date: 2026-02-27
Last updated on: 2026-03-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| statamic | statamic | From 6.0.0 (inc) to 6.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Statamic, a Laravel and Git powered content management system (CMS). In versions starting from 6.0.0 up to but not including 6.4.0, authenticated Control Panel users can, under certain conditions, bypass an intended verification step. This bypass allows them to obtain elevated privileges beyond what they should normally have.
Essentially, users who are already authenticated but have limited permissions may exploit this flaw to gain higher-level access without completing the required verification process.
This issue was fixed in version 6.4.0.
How can this vulnerability impact me? :
The vulnerability can lead to privilege escalation, meaning that users with limited permissions could gain access to sensitive operations or data that they should not be able to access.
Because the vulnerability allows bypassing verification steps, it can compromise the integrity and confidentiality of the system, potentially leading to unauthorized changes, data exposure, or disruption of services.
The CVSS score of 8.8 indicates a high severity impact, with potential consequences including complete compromise of confidentiality, integrity, and availability.
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 6.4.0 or later, where the issue has been fixed.