Skip to main content
VulnerabilityPublished Updated

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

Affects statamic cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 6.3.2 or 5.73.9 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.3.2, 5.73.9
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade statamic cms to 6.3.2 or 5.73.9.

Affected software

ProductAffectedFixed in
statamiccmsAffected
  • >=6.0.0-alpha.1 <6.3.2
Fixed in
  • 6.3.2
statamiccmsAffected
  • <5.73.9
Fixed in
  • 5.73.9

AI-suggested

To mitigate CVE-2026-27196, organizations should immediately upgrade Statamic CMS to versions 6.3.2 or 5.73.9 or later, where the vulnerability is patched. Additionally, restrict field management permissions to only trusted and necessary users to reduce the attack surface. Implement strict content validation and sanitization policies for user inputs, especially in HTML fieldtypes, to prevent injection of malicious scripts. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. Regularly audit user roles and permissions within the CMS to ensure least privilege principles are enforced. Monitor CMS logs for unusual activity related to content changes by field managers. Consider deploying web application firewalls (WAFs) with rules targeting XSS attack patterns as an additional layer of defense. Finally, educate CMS users about the risks of interacting with untrusted content and the importance of reporting suspicious behavior.

Description

Statmatic is a Laravel and Git powered content management system (CMS). Versions 5.73.8 and below in addition to 6.0.0-alpha.1 through 6.3.1 have a Stored XSS vulnerability in html fieldtypes which allows authenticated users with field management permissions to inject malicious JavaScript that executes when viewed by higher-privileged users. This issue has been fixed in 6.3.2 and 5.73.9.

References

Community reviews

Loading reviews…