CVE-2026-33172: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, a stored XSS vulnerability in SVG asset reuploads allows authenticated users with asset upload permissions to bypass SVG sanitization and inject malicious JavaScript that executes when the asset is viewed. This has been fixed in 5.73.14 and 6.7.0.
AI Analysis
Technical Summary
CVE-2026-33172 is a stored cross-site scripting (XSS) vulnerability identified in the Statamic content management system, which is built on Laravel and Git. The vulnerability affects versions prior to 5.73.14 and 6.7.0. It arises from improper neutralization of input during web page generation, specifically in the handling of SVG asset reuploads. Authenticated users with permissions to upload assets can exploit this flaw by uploading specially crafted SVG files that bypass the CMS's SVG sanitization process. When these malicious SVG assets are viewed within the CMS or by users, embedded JavaScript code executes in the context of the victim's browser. This can lead to session hijacking, credential theft, or further exploitation of the web application. The vulnerability requires the attacker to have authenticated access with asset upload rights and some user interaction to trigger the payload. The CVSS v3.1 score of 8.7 reflects a network attack vector with low complexity, requiring privileges and user interaction, and resulting in high confidentiality and integrity impacts but no availability impact. The vulnerability has been fixed in Statamic versions 5.73.14 and 6.7.0. No public exploit code or active exploitation has been reported to date.
Potential Impact
The impact of CVE-2026-33172 is significant for organizations using vulnerable versions of Statamic CMS. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the web application, potentially leading to theft of sensitive information such as authentication tokens, user credentials, or other confidential data. It can also facilitate further attacks like privilege escalation, phishing, or malware distribution within the affected environment. Since the vulnerability requires authenticated access with asset upload permissions, insider threats or compromised user accounts pose a substantial risk. The integrity of web content can be compromised, damaging organizational reputation and trust. Although availability is not directly affected, the indirect consequences of data breaches and trust erosion can be severe. Organizations relying on Statamic for public-facing or internal web portals are at risk of targeted attacks, especially if they have weak access controls or insufficient monitoring of asset uploads.
Mitigation Recommendations
To mitigate CVE-2026-33172, organizations should immediately upgrade Statamic CMS to versions 5.73.14 or 6.7.0 or later, where the vulnerability has been patched. Until upgrades can be applied, restrict asset upload permissions strictly to trusted users and review existing user roles to minimize the number of users with upload rights. Implement monitoring and alerting on asset upload activities, especially SVG file uploads, to detect suspicious or anomalous behavior. Employ web application firewalls (WAFs) with rules targeting SVG-based XSS payloads as a temporary defense layer. Conduct regular security audits of CMS configurations and user permissions. Educate users about the risks of uploading untrusted SVG content and enforce content sanitization policies where possible. Finally, maintain an incident response plan to quickly address any suspected exploitation attempts.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, Netherlands, France, India, Brazil, Japan
CVE-2026-33172: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
Description
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, a stored XSS vulnerability in SVG asset reuploads allows authenticated users with asset upload permissions to bypass SVG sanitization and inject malicious JavaScript that executes when the asset is viewed. This has been fixed in 5.73.14 and 6.7.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33172 is a stored cross-site scripting (XSS) vulnerability identified in the Statamic content management system, which is built on Laravel and Git. The vulnerability affects versions prior to 5.73.14 and 6.7.0. It arises from improper neutralization of input during web page generation, specifically in the handling of SVG asset reuploads. Authenticated users with permissions to upload assets can exploit this flaw by uploading specially crafted SVG files that bypass the CMS's SVG sanitization process. When these malicious SVG assets are viewed within the CMS or by users, embedded JavaScript code executes in the context of the victim's browser. This can lead to session hijacking, credential theft, or further exploitation of the web application. The vulnerability requires the attacker to have authenticated access with asset upload rights and some user interaction to trigger the payload. The CVSS v3.1 score of 8.7 reflects a network attack vector with low complexity, requiring privileges and user interaction, and resulting in high confidentiality and integrity impacts but no availability impact. The vulnerability has been fixed in Statamic versions 5.73.14 and 6.7.0. No public exploit code or active exploitation has been reported to date.
Potential Impact
The impact of CVE-2026-33172 is significant for organizations using vulnerable versions of Statamic CMS. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the web application, potentially leading to theft of sensitive information such as authentication tokens, user credentials, or other confidential data. It can also facilitate further attacks like privilege escalation, phishing, or malware distribution within the affected environment. Since the vulnerability requires authenticated access with asset upload permissions, insider threats or compromised user accounts pose a substantial risk. The integrity of web content can be compromised, damaging organizational reputation and trust. Although availability is not directly affected, the indirect consequences of data breaches and trust erosion can be severe. Organizations relying on Statamic for public-facing or internal web portals are at risk of targeted attacks, especially if they have weak access controls or insufficient monitoring of asset uploads.
Mitigation Recommendations
To mitigate CVE-2026-33172, organizations should immediately upgrade Statamic CMS to versions 5.73.14 or 6.7.0 or later, where the vulnerability has been patched. Until upgrades can be applied, restrict asset upload permissions strictly to trusted users and review existing user roles to minimize the number of users with upload rights. Implement monitoring and alerting on asset upload activities, especially SVG file uploads, to detect suspicious or anomalous behavior. Employ web application firewalls (WAFs) with rules targeting SVG-based XSS payloads as a temporary defense layer. Conduct regular security audits of CMS configurations and user permissions. Educate users about the risks of uploading untrusted SVG content and enforce content sanitization policies where possible. Finally, maintain an incident response plan to quickly address any suspected exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T22:16:36.719Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bdc1299e4ece4ed25050a5
Added to database: 3/20/2026, 9:50:33 PM
Last enriched: 3/27/2026, 10:40:24 PM
Last updated: 5/1/2026, 10:02:46 AM
Views: 57
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.
External Links
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.