CVE-2026-33172 Statamic has Stored XSS via SVG Sanitization Bypass

High 8.7 Published Updated

Authenticated users can inject malicious JavaScript via SVG uploads, leading to stored XSS when assets are viewed.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-33172?

CVE-2026-33172 is a high-severity cross-site scripting vulnerability in statamic cms, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-79

Which versions are affected by CVE-2026-33172?

4 open source packages ship an affected version, including statamic/cms. It affects 1 product.

PackageAffectedFixed in
statamic/cms PackagistAll versions5.73.14
statamic/cms PackagistAll versions5.73.14
statamic/cms PackagistFrom 6.0.0-alpha.16.7.0
statamic/cms PackagistFrom 6.0.0-alpha.16.7.0

Products include Statamic Statamic.

How do I fix CVE-2026-33172?

Upgrade statamic/cms to a fixed version for your release line: 5.73.14 or 6.7.0.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-33172 being exploited?

There is no known exploitation of CVE-2026-33172 in the wild and no public exploit code.

Sources

Also known as GHSA-7rcv-55mj-chg7.

Is CVE-2026-33172 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free