CVE-2026-41175 is a high-severity security vulnerability in statamic/cms (composer), affecting versions < 5.73.20. It is fixed in 5.73.20, 6.13.0.
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 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (5.73.20, 6.13.0). Upgrading removes the vulnerable code path.
composer
statamic/cms (< 5.73.20)statamic/cms (>= 6.0.0-alpha.1, < 6.13.0)statamic/cms → 5.73.20 (composer)statamic/cms → 6.13.0 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2026-41175 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2026-41175 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-41175 in your environment →Upgrade the following packages to resolve this vulnerability:
statamic/cms to 5.73.20 or laterstatamic/cms to 6.13.0 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-41175 is a high-severity security vulnerability in statamic/cms (composer), affecting versions < 5.73.20. It is fixed in 5.73.20, 6.13.0.
CVE-2026-41175 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
statamic/cms (composer) versions < 5.73.20 is affected.
Yes. CVE-2026-41175 is fixed in 5.73.20, 6.13.0. Upgrade to this version or later.
Whether CVE-2026-41175 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
statamic/cms to 5.73.20 or laterstatamic/cms to 6.13.0 or later