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.
Github GHSA