CVE-2025-64112
📋 TL;DR
CVE-2025-64112 is a stored cross-site scripting (XSS) vulnerability in Statmatic CMS that allows authenticated users with content creation permissions to inject malicious JavaScript into Collections and Taxonomies. When higher-privileged users view the compromised content, the malicious code executes in their browser context. This affects Statmatic CMS installations with authenticated content creators.
💻 Affected Systems
- Statmatic CMS
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Attackers could steal administrator session cookies, perform account takeover of privileged users, inject backdoors into the CMS, or redirect users to malicious sites.
Likely Case
Authenticated attackers with content creation access inject malicious scripts that execute when administrators or editors view the content, potentially leading to session hijacking or privilege escalation.
If Mitigated
With proper input validation and output encoding, malicious scripts are neutralized before execution, preventing any impact.
🎯 Exploit Status
Exploitation requires authenticated access but is technically simple once authenticated; weaponization is likely due to the common nature of stored XSS vulnerabilities.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 5.22.1
Vendor Advisory: https://github.com/statamic/cms/security/advisories/GHSA-g59r-24g3-h7cm
Restart Required: No
Instructions:
1. Update Statmatic CMS to version 5.22.1 or later using composer: 'composer require statamic/cms:^5.22.1'. 2. Clear application cache if needed. 3. Verify the update completed successfully.
🔧 Temporary Workarounds
Input Validation and Output Encoding
allImplement strict input validation on Collections and Taxonomies fields and ensure proper output encoding when displaying user-generated content.
Content Security Policy (CSP)
allImplement a strict Content Security Policy header to mitigate XSS impact by restricting script execution sources.
🧯 If You Can't Patch
- Restrict content creation permissions to trusted users only and implement principle of least privilege.
- Implement web application firewall (WAF) rules to detect and block XSS payloads in user inputs.
🔍 How to Verify
Check if Vulnerable:
Check if Statmatic CMS version is below 5.22.1 by examining composer.lock or running 'composer show statamic/cms'.Check Version:
composer show statamic/cms | grep versionsVerify Fix Applied:
Confirm version is 5.22.1 or higher and test Collections/Taxonomies with XSS payloads to ensure they are properly sanitized.📡 Detection & Monitoring
Log Indicators:
- Unusual content creation/modification patterns
- JavaScript payloads in Collection/Taxonomy fields in application logs
Network Indicators:
- Unexpected outbound connections from admin sessions following content viewing
SIEM Query:
source="application_logs" AND ("Collection" OR "Taxonomy") AND ("script" OR "javascript" OR "onerror" OR "onload")