statamic/cms security advisory

CVE-2026-27196: Statamic affected by privilege escalation via stored cross-site scripting

CVE-2026-27196 is a high-severity stored XSS vulnerability in the PHP package statamic/cms (CVSS 4.8), published 21 February 2026. It is fixed in 5.73.9 and 6.3.2, one per release line; earlier versions on each line are affected. Exploiting it needs an admin-level account.

high 4.8 published 2026-02-21 · updated 2026-06-17

Affected versions: < 5.73.9
>= 6.0.0-alpha.1, < 6.3.2
Fixed in: 5.73.9, 6.3.2
Newest release: 6.40.0
Severity: High · CVSS 4.8
Type: Stored cross-site scripting (XSS)
CWE-79
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your statamic/cms version affected?

Run composer show statamic/cms in your project, then enter the version. We check it against this and every other known statamic/cms advisory.

Who can exploit CVE-2026-27196

Access: A high-privilege account in the app, such as an admin.
Interaction: A user also has to do something, such as open a link or a page the attacker prepared.

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Your app is only exposed if it uses the affected part of statamic/cms. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-27196 in statamic/cms

Find the installed version: composer show statamic/cms. If you never required it yourself, composer why statamic/cms shows which package pulls it in.
Update it: composer update statamic/cms --with-all-dependencies. You need the fixed version for your release line (5.73.9 and 6.3.2).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "statamic/cms": "^6.3.2" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-27196.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for stored XSS issues while the upgrade waits. None of it replaces the fix.

Escape output in your own templates and add a Content-Security-Policy that blocks inline scripts.
Limit who can save the content the advisory names (for example rich text, SVG or form fields).
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-27196 advisory

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.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-27196. Advisory title: “Statamic affected by privilege escalation via stored cross-site scripting”.

References

GitHub advisory GHSA-8r7r-f4gm-wcpq github.com
Fix commit 11ae40e github.com
Fix commit 6c270da github.com

Other statamic/cms advisories

medium CVE-2026-71435: Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template 2026-08-06
medium CVE-2026-71434: Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types 2026-08-06
medium CVE-2026-64662: Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries 2026-08-06
medium CVE-2026-64663: Statamic: Unsafe method invocation via Antlers template resolution allows data destruction 2026-08-06
high CVE-2026-64665: Statamic: Account takeover via OAuth email matching without email-verification check 2026-08-06
medium CVE-2026-64664: Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence 2026-08-06

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.