Craft CMS — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/vendors/craft-cms/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 06 May 2026 17:49:17 +0000Craft CMS GraphQL Address Resolver Missing Authorization Allows PII Disclosurehttps://feed.craftedsignal.io/briefs/2026-05-craftcms-graphql-disclosure/Wed, 06 May 2026 17:49:17 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-craftcms-graphql-disclosure/A missing authorization check in the GraphQL Address element resolver of Craft CMS Pro allows a GraphQL API token scoped to a low-privilege user group to read all addresses in the system, including those belonging to users in groups the token is not authorized to access, exposing personally identifiable information (PII).A missing authorization check in Craft CMS Pro’s GraphQL Address element resolver (src/gql/resolvers/elements/Address.php) allows unauthorized access to sensitive user data. Specifically, a GraphQL API token with limited permissions (e.g., read access to a single low-privilege user group) can bypass intended scope restrictions and retrieve all addresses within the system. This includes addresses associated with users belonging to groups the token should not have access to, effectively exposing PII. This vulnerability affects Craft CMS Pro versions 4.0.0 through 5.9.17 and presents a significant risk to data confidentiality, especially for organizations using GraphQL APIs for headless CMS deployments. The issue was identified through manual source code review with AI-assisted analysis.

Attack Chain

  1. Attacker obtains a GraphQL API token with read access to at least one user group within Craft CMS.
  2. Attacker introspects the GraphQL schema using a query to discover the available top-level queries, including addresses.
  3. Attacker queries the AddressInterface to identify exposed fields, such as fullName, addressLine1, organization, and organizationTaxId, revealing potential PII.
  4. Attacker makes a baseline query to the GraphQL API using the token to confirm the token’s user scope is limited. This confirms the token only has access to a specific user group.
  5. Attacker issues a query to retrieve all addresses using the GraphQL API, bypassing intended scope restrictions.
  6. The API returns address data for ALL user groups, including those outside the token’s authorized scope, exposing PII of users in restricted groups.
  7. Attacker leverages the ownerId argument to perform an IDOR attack, targeting specific users’ addresses by their IDs without proper authorization.
  8. Attacker extracts sensitive address information, including corporate tax IDs, for internal users they should not have access to, completing the data exfiltration.

Impact

The vulnerability allows an attacker with minimal permissions to extract sensitive PII, including full names, home addresses, organizations, and tax IDs. This poses a direct threat to user data privacy and organizational security. All Craft CMS Pro sites (v4.0.0+) that use GraphQL API tokens with user group scoping and store user addresses are potentially affected. The targeted extraction via IDOR can lead to reconnaissance against high-value users like administrators. If successful, the attacker can gain unauthorized access to confidential information, leading to potential financial loss, reputational damage, and legal repercussions.

Recommendation

  • Upgrade Craft CMS to versions 5.9.18 or 4.17.12 or later to patch CVE-2026-44010.
  • Deploy the Sigma rule Detect CraftCMS GraphQL Address Resolver Unauthorized Access to your SIEM to detect exploitation attempts.
  • Review and restrict the permissions of GraphQL API tokens to follow the principle of least privilege, minimizing the potential impact of unauthorized access.
  • Monitor web server logs for unusual GraphQL queries targeting the addresses endpoint.
]]>highadvisorycraftcmsgraphqlpiidisclosureCraft CMS Authenticated Remote Code Execution via Malicious Attached Behaviorhttps://feed.craftedsignal.io/briefs/2024-01-craft-cms-rce/Tue, 02 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-craft-cms-rce/Craft CMS versions before 4.17.12 and 5.9.18 are vulnerable to authenticated remote code execution via malicious behavior injection in the field layout hydration path.Craft CMS versions before 4.17.12 and 5.9.18 are vulnerable to authenticated remote code execution. The vulnerability stems from an input-handling flaw in a Yii object creation path, allowing any authenticated user to inject malicious configuration and execute arbitrary commands on the server. This is achieved by exploiting the dynamic object configuration feature of Yii, which Craft CMS utilizes to build parts of itself from a settings list. This vulnerability is related to a previously disclosed issue (GHSA-255j-qw47-wjh5) but utilizes a different, unmitigated path. The attack exploits the condition field layouts data conversion to a live FieldLayout object without proper sanitization.

Attack Chain

  1. An authenticated user logs into the Craft CMS admin panel.
  2. The attacker crafts a malicious POST request to /admin/actions/element-search/search with a JSON payload.
  3. The JSON payload contains a condition parameter with a nested fieldLayouts array.
  4. Within the fieldLayouts array, the attacker injects a yii\\behaviors\\AttributeTypecastBehavior object with a __construct() method.
  5. The __construct() method contains the malicious configuration, including attributeTypes and typecastBeforeSave parameters.
  6. The typecastBeforeSave parameter is configured to execute a shell command (e.g., using /bin/bash -c).
  7. The server-side application processes the request and attempts to create a FieldLayout object from the provided configuration data.
  8. Due to the lack of sanitization, the malicious configuration is injected during object creation, leading to the execution of the attacker-controlled command.

Impact

Successful exploitation allows an attacker to execute arbitrary commands on the server with the privileges of the web server user. This can lead to complete compromise of the Craft CMS instance, including data theft, modification, or deletion. An attacker could also pivot to other systems on the network from the compromised server. There is no specific victim count or sector targeted mentioned, but any Craft CMS instance using a vulnerable version is susceptible.

Recommendation

  • Upgrade Craft CMS to version 4.17.12 or 5.9.18 or later to patch the vulnerability (Affected products).
  • Deploy the Sigma rule Detect Craft CMS RCE Attempt via Element Search to identify exploitation attempts in web server logs (rules).
  • Monitor POST requests to /admin/actions/element-search/search for suspicious JSON payloads, particularly those containing yii\\behaviors\\AttributeTypecastBehavior (Attack Chain).
]]>highadvisorycraft-cmsrcevulnerability