# CVE-2017-11422: Statamic framework Incorrect Permission Assignment

> Attackers can bypass permission checks to perform sensitive actions like resetting passwords or creating accounts in Statamic CMS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5m64-9hq5-5pf2

## What is CVE-2017-11422?

CVE-2017-11422 is a high-severity missing authorization vulnerability in n/a, published on 24 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-11422?

2 open source packages ship an affected version, including statamic/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 2.6.0 |
| `statamic/cms` | Packagist | All versions | 2.6.0 |

Products: Statamic Statamic.

## How do I fix CVE-2017-11422?

Upgrade statamic/cms to 2.6.0 or later.

## Is CVE-2017-11422 being exploited?

There is no known exploitation of CVE-2017-11422 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-45364](https://insights.sbomify.com/CVE-2021-45364/): Code injection in n/a (critical 9.8)
- [CVE-2026-27593](https://insights.sbomify.com/CVE-2026-27593/): Statamic is vulnerable to account takeover via password reset link injection (critical 9.3)
- [CVE-2026-27939](https://insights.sbomify.com/CVE-2026-27939/): Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass (high 8.8)
- [CVE-2023-48217](https://insights.sbomify.com/CVE-2023-48217/): Remote code execution via form uploads in statamic/cms (high 8.8)
- [CVE-2026-33172](https://insights.sbomify.com/CVE-2026-33172/): Statamic has Stored XSS via SVG Sanitization Bypass (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11422 and fix it if it is affected.

What it is: CVE-2017-11422 is a high-severity missing authorization vulnerability in n/a, published on 24 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11422 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 2.6.0
- statamic/cms (Packagist): affected all versions; fixed in 2.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11422/ (Markdown: https://insights.sbomify.com/CVE-2017-11422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11422
- OSV: https://osv.dev/vulnerability/CVE-2017-11422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11422/
Summaries are generated and may contain mistakes; the official description above is the record.