Skip to main content
VulnerabilityPublished

CVE-2025-64112: statamic cms · Cross-site Scripting

Affects statamic cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High : upgrade to 5.22.1 soon.

Data as of 26 Oct 2026, 09:08 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade statamic/cms to 5.22.1.

Affected software

ProductAffectedFixed in
GitHubstatamic/cmspkg:github/statamic/cmsOther threatsAffected
  • <5.22.1
Fixed in
  • 5.22.1

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

AI-suggested

1. Immediately upgrade all Statamic CMS instances to version 5.22.1 or later to apply the official patch addressing this vulnerability. 2. Restrict content creation permissions strictly to trusted users and regularly review user roles to minimize the attack surface. 3. Implement Content Security Policy (CSP) headers to reduce the impact of potential XSS payloads by restricting script execution sources. 4. Conduct regular audits of Collections and Taxonomies content for suspicious or unexpected script injections. 5. Employ web application firewalls (WAF) with rules tuned to detect and block XSS payloads targeting Statamic CMS. 6. Monitor logs and user activity for anomalous behavior indicative of exploitation attempts or privilege escalation. 7. Educate content creators and administrators about the risks of XSS and safe content handling practices. 8. Consider implementing multi-factor authentication (MFA) for CMS access to reduce risk from compromised credentials. 9. Isolate the CMS environment from critical backend systems to limit lateral movement in case of compromise.

Description

Statmatic is a Laravel and Git powered content management system (CMS). Stored XSS vulnerabilities in Collections and Taxonomies allow authenticated users with content creation permissions to inject malicious JavaScript that executes when viewed by higher-privileged users. This vulnerability is fixed in 5.22.1.

References

Community reviews

Loading reviews…