VulnerabilityPublished 12 Mar 2026

CVE-2026-32612: statamic cms · Cross-site Scripting

Affects statamic cmsSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 6.6.2 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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 12 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 30 Oct 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 and statamic/cms to 6.6.2.

Affected software

Product	Affected	Fixed in
statamiccms	Affected >=6.0.0 <6.6.2	Fixed in 6.6.2
GitHubstatamic/cms`pkg:github/statamic/cms`Other threats	Affected <6.6.2	Fixed in 6.6.2

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

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade Statamic CMS to version 6.6.2 or later, where the issue is patched. Until the upgrade can be performed, restrict control panel access to trusted users only and limit the use of the impersonation feature to essential cases with strict monitoring. Implement strong authentication mechanisms and session management to reduce the risk of session hijacking. Conduct regular audits of user permissions and control panel activity logs to detect suspicious behavior. Additionally, apply web application firewall (WAF) rules that can detect and block common XSS payload patterns targeting the control panel. Educate administrators about the risks of impersonation and encourage cautious use of this feature. Finally, ensure that input validation and output encoding best practices are followed in custom plugins or extensions to prevent similar vulnerabilities.

Description

CVE-2026-32612 is a stored cross-site scripting (XSS) vulnerability in Statamic CMS versions 6.0.0 up to but not including 6.6.2. It affects the control panel color mode preference feature, allowing authenticated users with control panel access to inject malicious JavaScript. This script executes when a higher-privileged user impersonates the compromised account, potentially leading to session hijacking or privilege escalation. The vulnerability requires authentication and user interaction (impersonation). It has a CVSS score of 5.4 (medium severity) and was fixed in version 6.

Impact

The primary impact of this vulnerability is the potential for attackers with low-level authenticated access to inject malicious JavaScript that executes in the context of higher-privileged users during impersonation. This can lead to session hijacking, theft of sensitive information, unauthorized actions within the CMS, and possible privilege escalation. Organizations using affected Statamic versions risk compromise of their CMS control panels, which could lead to website defacement, data leakage, or further infiltration into internal networks. Since the vulnerability requires authentication and user interaction, the attack surface is somewhat limited; however, in environments where multiple users have control panel access or impersonation is frequently used, the risk is elevated. The vulnerability does not affect availability directly but compromises confidentiality and integrity. Given Statamic’s use in various industries for content management, the impact can be significant, especially for organizations with sensitive or high-profile web content.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
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.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:29 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats