CVE-2026-41175: Statamic Unsafe Method Invocation Vulnerability

HIGH
Advisory Identifier: GHSA-4jjr-vmv7-wh4w
Share
CVSS 8.1
CWE-470
Published
Advisory Summary

CVE-2026-41175 is a HIGH (CVSS 8.1) unsafe method invocation vulnerability (CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')) affecting Statamic libraries in the Packagist ecosystem. The issue involves unsafe method invocation via query value resolution allows data destruction. Remediation is available by upgrading affected packages to version 5.73.20, 6.13.0.

CVE-2026-41175 at a Glance

CVE Identifier CVE-2026-41175
GHSA Identifier GHSA-4jjr-vmv7-wh4w
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Affected Product Statamic
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-41175

To remediate this vulnerability, upgrade all affected Statamic dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

statamic/cms fixed: 5.73.20 
Upgrade statamic/cms to 5.73.20
statamic/cms fixed: 6.13.0 
Upgrade statamic/cms to 6.13.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for statamic/cms

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-41175, inspect your project dependencies for Statamic:

inspect dependencies for statamic/cms

Analyze the terminal output to locate any version of Statamic in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.73.20), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection'), where the product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. In Statamic, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. ### Patches This has been fixed in 5.73.20 and 6.13.0.

CVE-2026-41175 Affected Statamic Versions

2 component(s)
Fixed Versions:
5.73.206.13.0
Product / Package Ecosystem Affected Versions Fixed Version
statamic/cms
 Packagist
< 5.73.20
5.73.20
statamic/cms
 Packagist
≥ 6.0.0-alpha.1
< 6.13.0
6.13.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w
NVD — CVE-2026-41175 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-41175
Statamic Source Repository REPOSITORY
https://github.com/statamic/cms

Frequently Asked Questions

What is CVE-2026-41175?
CVE-2026-41175 is a security vulnerability in Statamic involving Unsafe method invocation via query value resolution allows data destruction under CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection').
Which Statamic versions are affected?
Affected versions include releases prior to 5.73.20, 6.13.0 across affected packages: statamic/cms.
What version fixes CVE-2026-41175?
Upgrading to 5.73.20, 6.13.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is statamic/cms affected?
Yes, statamic/cms is affected in releases prior to 5.73.20, 6.13.0. Upgrade your dependency to 5.73.20, 6.13.0 or later.
What is the CVSS score of CVE-2026-41175?
CVE-2026-41175 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-41175?
CVE-2026-41175 is classified under CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') (The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.).
How can I check Packagist dependencies for CVE-2026-41175?
Run the dependency tree command: 'inspect dependencies for statamic/cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4jjr-vmv7-wh4w",
  "modified" : "2026-04-24T20:52:04Z",
  "published" : "2026-04-16T21:25:35Z",
  "aliases" : [ "CVE-2026-41175" ],
  "summary" : "Statamic: Unsafe method invocation via query value resolution allows data destruction",
  "details" : "### Impact\n\nManipulating 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.\n\nThe 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.\n\nThe 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.\n\nSites that enable the REST or GraphQL API without authentication should treat patching as critical priority.\n\n### Patches\n\nThis has been fixed in 5.73.20 and 6.13.0.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "statamic/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.73.20"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "statamic/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0-alpha.1"
      }, {
        "fixed" : "6.13.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41175"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/statamic/cms"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-470" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-16T21:25:35Z",
    "nvd_published_at" : "2026-04-22T22:16:31Z"
  }
}