
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-27939 is a privilege escalation vulnerability in Statamic CMS, a Laravel and Git-powered content management system, caused by an improper authentication bypass in the Control Panel. Authenticated users with low-level privileges may, under certain conditions, obtain elevated privileges without completing the intended verification step, enabling access to sensitive operations. The vulnerability affects Statamic CMS versions 6.0.0 through 6.3.x (prior to 6.4.0) and was disclosed on February 27, 2026. It carries a CVSS v3.1 base score of 8.8 (High) (Github Advisory, Statamic Advisory).
The root cause is classified as CWE-287 (Improper Authentication) — the application fails to sufficiently verify a user's identity or authorization level before granting access to elevated operations. Based on the patch commit, the vulnerability involves two related weaknesses: (1) the Control Panel's authentication exception handler would redirect users to an externally-supplied Referer header URL without validating whether it was internal to the application, and (2) form submission handlers accepted attacker-controlled _redirect and _error_redirect parameters that could point to external URLs, enabling open redirect abuse. The fix hardened these redirect paths by adding URL::isExternalToApplication() checks to prevent external redirects, which could be chained to bypass the intended elevated-session verification step (Statamic Advisory, Patch Commit).
Successful exploitation allows an authenticated attacker with low-level Control Panel access to bypass the intended privilege verification step and gain elevated privileges within the Statamic CMS Control Panel. This could enable unauthorized access to sensitive administrative operations, modification of site content or configuration, access to confidential data, and potentially full administrative control depending on the victim's permission structure. The high confidentiality, integrity, and availability impact scores reflect the potential for complete compromise of the CMS instance (Github Advisory, Statamic Advisory).
As of the time of disclosure, there is no public proof-of-concept exploit code and no evidence of active in-the-wild exploitation (Feedly). The vulnerability requires an authenticated attacker with at least low-level Control Panel access, which limits the attack surface compared to unauthenticated vulnerabilities. The EPSS score is approximately 0.022% (6th percentile), indicating a low near-term probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The vulnerability was reported by security researcher Mistz1 (Github Advisory).
Referer HTTP header pointing to an attacker-controlled external URL. The vulnerable redirect handler in RendersControlPanelExceptions.php would redirect the user to this external URL without validating it as internal, potentially bypassing the verification step._redirect or _error_redirect parameter pointing to an attacker-controlled URL to exploit the open redirect in FormController.php.Referer headers pointing to external domains; form POST requests to /!/forms/<form-handle> containing _redirect or _error_redirect parameters with external URLs (e.g., https://evil.com/...).Statamic has released version 6.4.0 which fixes this vulnerability by adding external URL validation to redirect handlers in both the Control Panel exception renderer and the form submission controller. All users running Statamic CMS versions 6.0.0 through 6.3.x should upgrade to version 6.4.0 or later immediately. As an interim measure, administrators should restrict Control Panel access to only trusted and necessary users, and review Control Panel access logs for any suspicious privilege escalation activity prior to patching (Github Advisory, Patch Commit).
The vulnerability received coverage from The Hacker Wire, which published an article on the Statamic CMS privilege escalation (The Hacker Wire). Social media discussion was observed on Bluesky and Mastodon, primarily from automated CVE tracking accounts. Overall community reaction was measured, consistent with the limited exploitation risk given the authentication prerequisite and absence of a public PoC.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."