What is the severity of CVE-2017-11422?

CVE-2017-11422 is considered a high severity vulnerability due to potential unauthorized user actions.

How do I fix CVE-2017-11422?

To fix CVE-2017-11422, upgrade the Statamic framework to version 2.6.0 or later.

What are the implications of CVE-2017-11422?

CVE-2017-11422 allows unauthorized users to invoke sensitive methods, potentially compromising application security.

Who is affected by CVE-2017-11422?

CVE-2017-11422 affects all users running Statamic versions prior to 2.6.0.

What methods are vulnerable in CVE-2017-11422?

CVE-2017-11422 relates to vulnerable methods such as reset password, create new account, and create new role.

Vulnerability/
CVE-2017-11422

high

8.8

CWE

732

24/7/2017

13/5/2022

5/8/2024

CVE-2017-11422

First published: Mon Jul 24 2017(Updated: )

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.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Statamic Statamic	<2.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-11422?
CVE-2017-11422 is considered a high severity vulnerability due to potential unauthorized user actions.
How do I fix CVE-2017-11422?
To fix CVE-2017-11422, upgrade the Statamic framework to version 2.6.0 or later.
What are the implications of CVE-2017-11422?
CVE-2017-11422 allows unauthorized users to invoke sensitive methods, potentially compromising application security.
Who is affected by CVE-2017-11422?
CVE-2017-11422 affects all users running Statamic versions prior to 2.6.0.
What methods are vulnerable in CVE-2017-11422?
CVE-2017-11422 relates to vulnerable methods such as reset password, create new account, and create new role.

collector/github-advisory-latest
alias/GHSA-5m64-9hq5-5pf2
alias/CVE-2017-11422
collector/github-advisory
collector/nvd-index
collector/nvd-cve
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/references
agent/severity
agent/last-modified-date
agent/description
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
package-manager/composer
vendor/statamic
canonical/statamic statamic

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-11422?
CVE-2017-11422 is considered a high severity vulnerability due to potential unauthorized user actions.
How do I fix CVE-2017-11422?
To fix CVE-2017-11422, upgrade the Statamic framework to version 2.6.0 or later.
What are the implications of CVE-2017-11422?
CVE-2017-11422 allows unauthorized users to invoke sensitive methods, potentially compromising application security.
Who is affected by CVE-2017-11422?
CVE-2017-11422 affects all users running Statamic versions prior to 2.6.0.
What methods are vulnerable in CVE-2017-11422?
CVE-2017-11422 relates to vulnerable methods such as reset password, create new account, and create new role.