Shopify App: Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps
Only affects shopify_app 22.1.0 up to 23.0.3 in apps using token-exchange authentication that rely on the shop parameter for authorization or data access. Fixed in 23.0.3.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 23.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Shopify App Rails engine (shopify_app) is affected when applications use its token-exchange authentication and rely on the request's shop parameter for authorization or tenant lookup. An attacker with a valid session for one Shopify store could potentially access another store's data or perform actions on it.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Shopify shopify_app
From 22.1.0 · fixed in 23.0.3
- shopify_appRubyGems
From 22.1.0 · fixed in 23.0.3
References 4
GitHub · Shopify/shopify_app
Questions about CVE-2026-63414
What does this mean?
A token-exchange request can be tied to the wrong shop context, so one shop's session may reach another shop's data or actions. The impact depends on how the application models authorization.Source: github.com
Am I affected, and how do I check?
Versions 22.1.0 up to but not including 23.0.3 of shopify_app are affected, in apps that use token-exchange authentication and use current_shopify_domain or the request shop parameter for authorization, tenant lookup, stored access-token selection, or shop-scoped data access. Check the shopify_app version in Gemfile.lock and whether the app uses token-exchange authentication.Source: github.com
What should I do about it?
Upgrade shopify_app to version 23.0.3. If an upgrade is not possible yet, the advisory's workaround is to use the authenticated shop from the verified ID token or session and reject a mismatched params[:shop] with 401 Unauthorized in token-exchange controllers.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data