Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Github access token exposureAnalysed#1087489 | Valid | No weakness recorded | – | 2021-07-26 | $50,000 | 1,601 |
| DoS Vulnerability via Cache Poisoning on cdn.shopify.com and shopify-assets.shopifycdn.comAnalysed#1695604 | Valid | Other weaknesses | Medium | 2025-06-04 | $3,800 | 266 |
| XSS at jamfpro.shopifycloud.comAnalysed#1444682 | Valid | Cross-site Scripting | – | 2023-02-02 | $9,400 | 240 |
| H1514 [*.(my)shopify.com] - Viewing Password Protected ContentAnalysed#421859 | Valid | Authentication | – | 2019-05-22 | $3,000 | 192 |
| XSS at https://exchangemarketplace.com/blogsearchAnalysed#1145162 | Valid | Cross-site Scripting | – | 2021-04-09 | – | 174 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (348 analysed so far), which can be wrong. Data as of 2026-11-14.