Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| authenticity token not verfied leads to change business nameAnalysed#994504 | Valid | Cross-Site Request Forgery | Medium | 2020-10-23 | $1,900 | 54 |
| apps.shopify.com - CSRF token leakage through Google AnalyticsAnalysed#196458 | Valid | Cross-Site Request Forgery | – | 2017-02-07 | – | 48 |
| [h1-2102] Wholesale - CSRF to Generate Invitation Token for a Customer and Move Customer to Invited StatusAnalysed#1091209 | Valid | Cross-Site Request Forgery | Low | 2021-12-06 | – | 34 |
| CSRF in all API endpoints when authenticated using HTTP AuthenticationAnalysed#195156 | Valid | Cross-Site Request Forgery | – | 2017-03-28 | – | 30 |
| H1514 CSRF in Domain transfer allows adding your domain to other user's accountAnalysed#416978 | Valid | Cross-Site Request Forgery | High | 2020-03-30 | – | 23 |
| Twitter Disconnect CSRFAnalysed#111216 | Valid | Cross-Site Request Forgery | – | 2016-02-01 | – | 18 |
| SVG parser loads external resources on image uploadAnalysed#97501 | Valid | Cross-Site Request Forgery | – | 2016-06-02 | – | 15 |
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, where there is one, which can be wrong. Data as of 2026-11-15.