statamic/cms security advisory

CVE-2026-41175: Statamic: Unsafe method invocation via query value resolution allows data destruction

CVE-2026-41175 is a high-severity security vulnerability in the PHP package statamic/cms (CVSS 8.1), published 22 April 2026. It is fixed in 5.73.20 and 6.13.0, one per release line; earlier versions on each line are affected. Exploiting it needs a low-privilege user account.

high 8.1 published 2026-04-22 · updated 2026-10-26

Affected versions: < 5.73.20
>= 6.0.0-alpha.1, < 6.13.0
Fixed in: 5.73.20, 6.13.0
Newest release: 6.40.0
Severity: High · CVSS 8.1
Type: Security issue
CWE-470
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-41175

Access: A normal, low-privilege user account in the app.

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

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-41175 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.20 and 6.13.0).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "statamic/cms": "^6.13.0" 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-41175.
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 this kind of issue while the upgrade waits. None of it replaces the fix.

If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-41175 advisory

Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.20 and 6.13.0, manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts. The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc. The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too. Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority. This has been fixed in 5.73.20 and 6.13.0.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-41175. Advisory title: “Statamic: Unsafe method invocation via query value resolution allows data destruction”.

References

GitHub advisory GHSA-4jjr-vmv7-wh4w 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.