LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11422: Statamic framework before 2.6.0 does not correctly check a session's permissions when the methods from a us...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Statamic versions before 2.6.0 had an authorization flaw around user-related actions. A session could reach methods such as password reset, account creation, or role creation without correct permission checks. For a business, the concern is unauthorized account or role changes in older Statamic sites.

Executive priority

Prioritize if the organization still runs legacy Statamic. The issue touches identity and role management, so compromise could affect site control. If Statamic is not present, priority is low after inventory confirmation.

Technical view

The CVE describes improper permission validation when methods from a Statamic user class are called. Listed sensitive methods include reset password, create new account, and create new role. Public data does not provide CVSS, CWE, detailed prerequisites, or confirmed affected configurations beyond Statamic framework before 2.6.0.

Likely exposure

Exposure is most likely limited to internet-facing or internally accessible Statamic deployments running versions before 2.6.0. The source bundle does not identify specific editions, plugins, default configurations, or hosting patterns.

Exploitation context

CISA KEV is false, and the provided sources do not claim active exploitation. A public gist is referenced, but the bundle does not provide enough detail to assess exploit maturity without reviewing beyond the supplied material.

Researcher notes

Evidence is sparse. The CVE description indicates an authorization flaw in user-class methods, but lacks CVSS, CWE, endpoint details, exploit prerequisites, and configuration scope. Avoid assuming active exploitation or broader product impact without additional vendor or primary-source confirmation.

Mitigation direction

  • Identify any Statamic deployments and their exact versions.
  • Upgrade versions before 2.6.0 according to Statamic vendor guidance.
  • Review user, role, and password reset activity for suspicious changes.
  • Restrict administrative access paths where feasible until upgraded.
  • Back up site content and configuration before remediation.

Validation and detection

  • Confirm no production Statamic instance is below version 2.6.0.
  • Check whether unexpected accounts or roles were created.
  • Review password reset logs or audit trails if available.
  • Verify administrative functions enforce role-based permissions after upgrade.
  • Document findings, upgrade evidence, and remaining unknowns.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-11422 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.