CVE-2026-27196: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
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.
AI Analysis
Technical Summary
CVE-2026-27196 is a stored cross-site scripting (XSS) vulnerability classified under CWE-79 affecting Statamic CMS, a Laravel and Git-powered content management system. The vulnerability resides in the html fieldtypes component of Statamic versions 5.73.8 and earlier, as well as versions from 6.0.0-alpha.1 up to 6.3.1. Authenticated users who possess field management permissions can inject malicious JavaScript code into the CMS content fields. When higher-privileged users, such as administrators or editors, view the compromised content, the injected script executes within their browsers. This can lead to session hijacking, credential theft, or unauthorized actions performed with elevated privileges. The vulnerability requires both authentication and user interaction (viewing the malicious content) but does not require complex attack vectors or advanced exploitation techniques. The issue has been addressed and patched in Statamic versions 6.3.2 and 5.73.9. The CVSS v3.1 base score of 8.1 reflects the high impact on confidentiality and integrity, with network attack vector, low attack complexity, and high privileges required. No public exploits have been reported yet, but the vulnerability poses a significant risk in multi-user environments where privilege separation exists.
Potential Impact
The impact of CVE-2026-27196 is substantial for organizations using affected Statamic CMS versions. Successful exploitation allows attackers with moderate privileges to execute arbitrary JavaScript in the context of higher-privileged users, potentially leading to credential theft, session hijacking, unauthorized data access, and privilege escalation. This compromises the confidentiality and integrity of sensitive information managed within the CMS. Since the vulnerability does not affect availability directly, denial-of-service is less likely. However, the breach of trust and potential for lateral movement within the CMS environment can lead to broader organizational compromise. Organizations with complex user roles and sensitive content hosted on Statamic CMS are at heightened risk. The vulnerability could also facilitate supply chain attacks if the CMS is used to manage content for external-facing websites or portals.
Mitigation Recommendations
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.
Affected Countries
United States, United Kingdom, Germany, France, Canada, Australia, Netherlands, Sweden, Japan, South Korea
CVE-2026-27196: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-27196 is a stored cross-site scripting (XSS) vulnerability classified under CWE-79 affecting Statamic CMS, a Laravel and Git-powered content management system. The vulnerability resides in the html fieldtypes component of Statamic versions 5.73.8 and earlier, as well as versions from 6.0.0-alpha.1 up to 6.3.1. Authenticated users who possess field management permissions can inject malicious JavaScript code into the CMS content fields. When higher-privileged users, such as administrators or editors, view the compromised content, the injected script executes within their browsers. This can lead to session hijacking, credential theft, or unauthorized actions performed with elevated privileges. The vulnerability requires both authentication and user interaction (viewing the malicious content) but does not require complex attack vectors or advanced exploitation techniques. The issue has been addressed and patched in Statamic versions 6.3.2 and 5.73.9. The CVSS v3.1 base score of 8.1 reflects the high impact on confidentiality and integrity, with network attack vector, low attack complexity, and high privileges required. No public exploits have been reported yet, but the vulnerability poses a significant risk in multi-user environments where privilege separation exists.
Potential Impact
The impact of CVE-2026-27196 is substantial for organizations using affected Statamic CMS versions. Successful exploitation allows attackers with moderate privileges to execute arbitrary JavaScript in the context of higher-privileged users, potentially leading to credential theft, session hijacking, unauthorized data access, and privilege escalation. This compromises the confidentiality and integrity of sensitive information managed within the CMS. Since the vulnerability does not affect availability directly, denial-of-service is less likely. However, the breach of trust and potential for lateral movement within the CMS environment can lead to broader organizational compromise. Organizations with complex user roles and sensitive content hosted on Statamic CMS are at heightened risk. The vulnerability could also facilitate supply chain attacks if the CMS is used to manage content for external-facing websites or portals.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-18T19:47:02.154Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69993c53be58cf853b46cc2b
Added to database: 2/21/2026, 5:02:11 AM
Last enriched: 2/28/2026, 12:38:18 PM
Last updated: 4/7/2026, 1:38:31 PM
Views: 55
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.