statamic/cms

CVE-2017-11422

CVE-2017-11422 is a high-severity incorrect permission assignment for critical resource vulnerability in statamic/cms (composer), affecting versions < 2.6.0. It is fixed in 2.6.0.

Key facts
CVSS score
8.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
statamic/cms
Fixed in
2.6.0
Disclosed
2017

Summary

Statamic framework before 2.6.0 does not correctly check a session's permissions when the methods from a user's class are called. Problematic methods include reset password, create new account, create new role, etc.

Impact

What is incorrect permission assignment for critical resource?

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

Severity and exposure

CVE-2017-11422 has a CVSS score of 8.8 (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 (2.6.0). Upgrading removes the vulnerable code path.

Affected versions

composer

  • statamic/cms (< 2.6.0)

Security releases

  • statamic/cms → 2.6.0 (composer)
Kodem intelligence

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 runtime-powered SCA identifies whether CVE-2017-11422 is reachable in your applications. Explore open-source security for your team.

See if CVE-2017-11422 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2017-11422 in your environment

Remediation advice

Upgrade statamic/cms to 2.6.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2017-11422

What is CVE-2017-11422?

CVE-2017-11422 is a high-severity incorrect permission assignment for critical resource vulnerability in statamic/cms (composer), affecting versions < 2.6.0. It is fixed in 2.6.0. A file, directory, or other resource is assigned permissions that allow broader access than intended.

How severe is CVE-2017-11422?

CVE-2017-11422 has a CVSS score of 8.8 (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.

Which versions of statamic/cms are affected by CVE-2017-11422?

statamic/cms (composer) versions < 2.6.0 is affected.

Is there a fix for CVE-2017-11422?

Yes. CVE-2017-11422 is fixed in 2.6.0. Upgrade to this version or later.

Is CVE-2017-11422 exploitable, and should I be worried?

Whether CVE-2017-11422 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

What actually determines whether CVE-2017-11422 is exploitable, and how bad it is?

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.

How do I fix CVE-2017-11422?

Upgrade statamic/cms to 2.6.0 or later.

Stop the waste.
Protect your environment with Kodem.