CVE-2026-63414

Shopify App: Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps

Published Oct 30, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
Shopify App is a Rails engine for building Shopify applications. From 22.1.0 until 23.0.3, `token-exchange` authenticated controllers can expose a request-derived `shop` context instead of the identity from a verified Shopify ID token or active Shopify session. `current_shopify_domain` can resolve to the sanitized `shop` query parameter, so a request authenticated for one `shop` can cause application code to treat a different requested `shop` as current. Affected applications use `shopify_app` `token-exchange` authentication, accept authenticated requests with a `shop` query parameter, and rely on `current_shopify_domain` or `params[:shop]` for authorization, tenant lookup, stored access-token selection or `shop`-scoped data access. An attacker with a valid Shopify session token for one `shop` can supply another `shop` in that parameter and potentially obtain unauthorized application data or perform `shop`-scoped actions, depending on the application's authorization model. This issue is fixed in version 23.0.3.

Analysis

AI-generated

Technical impact

Based on the description, it is inferred that the Shopify App Rails engine’s token‑exchange mechanism, between releases 22.1.0 and 23.0.3, mistakenly accepts a shop identifier supplied in the request query string rather than the trusted one from a verified Shopify ID token or active session. This misbinding leads to a post‑authentication authorization bypass: an attacker who already holds a valid Shopify session token for one shop can supply a different shop value in that parameter and cause the application to treat the request as belonging to the other shop. The consequence is unauthorized access to shop‑scoped data or actions, and a potential theft of sensitive confidential data.

Affected Systems

Affected systems are Shopify’s shopify_app Ruby on Rails engine used by Shopify app developers. Versions from 22.1.0 up through 23.0.3 contain the vulnerability. Any application that relies on token‑exchange authentication, accepts a shop query parameter, and uses current_shopify_domain or params[:shop] for tenant lookup, authorization, or data access without additional checks is impacted. Updating to 23.0.3 or later removes the flaw.

Risk and Exploitability

The CVSS base score of 7.6 indicates a high severity. Based on the description, it is inferred that the exploitation probability is very low (EPSS <1%), and the attack surface is limited to accounts that have already authenticated. The vulnerability requires an attacker to possess a legitimate Shopify session token for one shop, after which the attacker can pivot to any other shop by manipulating the query parameter. Because the attack uses a legitimate session, the attacker may indirectly bypass cross‑shop authorization and gain significant data exposure. It is not currently listed in the CISA KEV catalog. The risk remains high for any app exposed to the token‑exchange route that has not yet been patched.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade shopify_app to version 23.0.3 or later to remove the vulnerability.
  • Adjust token‑exchange configuration so that the shop context is derived solely from the verified Shopify ID token or active session and reject requests that supply a different shop query parameter.
  • If an upgrade is not immediately possible, add server‑side validation to ensure that current_shopify_domain (or params[:shop]) matches the authenticated session’s shop domain, and terminate any request that does not match.

Generated by OpenCVE AI on November 6, 2026 at 15:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6j52-38f8-qhxr Shopify App: Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps
History
Type Values Removed Values Added
Weaknesses CWE-639
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Shopify
Shopify shopify App
Vendors & Products Shopify
Shopify shopify App
Type Values Removed Values Added
Description Shopify App is a Rails engine for building Shopify applications. From 22.1.0 until 23.0.3, `token-exchange` authenticated controllers can expose a request-derived `shop` context instead of the identity from a verified Shopify ID token or active Shopify session. `current_shopify_domain` can resolve to the sanitized `shop` query parameter, so a request authenticated for one `shop` can cause application code to treat a different requested `shop` as current. Affected applications use `shopify_app` `token-exchange` authentication, accept authenticated requests with a `shop` query parameter, and rely on `current_shopify_domain` or `params[:shop]` for authorization, tenant lookup, stored access-token selection or `shop`-scoped data access. An attacker with a valid Shopify session token for one `shop` can supply another `shop` in that parameter and potentially obtain unauthorized application data or perform `shop`-scoped actions, depending on the application's authorization model. This issue is fixed in version 23.0.3.
Title Shopify App: Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps
Weaknesses CWE-863
References
Metrics cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 5, 2026, 3:01 AM
Reserved
Jul 16, 2026, 7:20 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 11:17 PM
Modified
Nov 5, 2026, 4:17 AM
Severity
Important
Public date
Oct 30, 2026, 10:49 PM