LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27939: Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass

Statmatic is a Laravel and Git powered content management system (CMS). Starting in version 6.0.0 and prior to version 6.4.0, Authenticated Control Panel users may under certain conditions obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and, depending on the user’s existing permissions, may lead to privilege escalation. This has been fixed in 6.4.0.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Statamic CMS versions 6.0.0 through before 6.4.0 allow authenticated Control Panel users to bypass an intended elevated-session verification step. This may let a logged-in user reach sensitive administrative actions beyond what was intended. The vendor fixed the issue in 6.4.0.

Executive priority

Prioritize patching in the next regular security window, sooner for internet-facing or multi-user editorial environments. The issue requires an authenticated user but has high potential impact across confidentiality, integrity, and availability.

Technical view

CVE-2026-27939 is a CWE-287 authentication flaw in Statamic CMS. The issue affects Statamic >=6.0.0 and <6.4.0. It requires low privileges, no user interaction, and is network-reachable according to CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8.

Likely exposure

Exposure is limited to organizations running Statamic CMS 6.x before 6.4.0 with authenticated Control Panel users. Risk is higher where many editors, contractors, or shared administrative accounts have panel access.

Exploitation context

Sources describe privilege escalation by authenticated Control Panel users under certain conditions. The CVE is not marked KEV, and the provided sources do not state active exploitation or public exploit availability.

Researcher notes

The public description does not define the exact conditions for bypass, and exploit details should not be inferred. The fixing commit and GitHub advisory are the best sources for code-level triage and regression validation.

Mitigation direction

  • Upgrade Statamic CMS to version 6.4.0 or later.
  • Review vendor advisory GHSA-rw9x-pxqx-q789 for current guidance.
  • Limit Control Panel access to trusted users until upgraded.
  • Review and remove unnecessary Control Panel accounts and permissions.

Validation and detection

  • Inventory Statamic CMS instances and identify versions >=6.0.0 and <6.4.0.
  • Confirm upgraded systems report Statamic CMS 6.4.0 or later.
  • Review Control Panel user lists for unnecessary or stale access.
  • Check administrative activity logs for unexpected sensitive operations.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27939 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-27939Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
statamiccms>= 6.0.0, < 6.4.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.