GHSA-jqh7-w5pr-cr56 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in @shopify/koa-shopify-auth. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @shopify/koa-shopify-auth — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jqh7-w5pr-cr56 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@shopify/koa-shopify-authnpmDescription
A cross-site scripting vulnerability exists in koa-shopify-auth v3.1.61-v3.1.62 that allows an attacker to inject JS payloads into the shop parameter on the /shopify/auth/enable_cookies endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @shopify/koa-shopify-auth | ≥ 3.1.61&&< 3.1.63 | 3.1.63npm install @shopify/koa-shopify-auth@3.1.63 |
Affected Products
koa-shopify-authshopifyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @shopify/koa-shopify-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @shopify/koa-shopify-auth to 3.1.63 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqh7-w5pr-cr56 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-jqh7-w5pr-cr56 in your dependencies?
Find it across npm, including transitive dependencies.