Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Program | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|---|
| Arbitrary Local-File Read from Admin - Restore From Backup due to SymlinksAnalysed#213558 | Valid | Discourse | Information Disclosure | High | 2017-05-13 | $512 | 52 |
| Disclosure of Program email Title Report when being removed as contributor. Bypass for Report #645264Analysed#669776 | Valid | HackerOne | Information Disclosure | Low | 2019-09-06 | – | 39 |
| [h1-2102] shopApps query from the graphql at /users/api returns all existing created apps, including private onesAnalysed#1085332 | Valid | Shopify | Information Disclosure | Medium | 2022-07-15 | $1,900 | 35 |
| Program Email Nofication settings ignored when being added as an external contributorAnalysed#645264 | Valid | HackerOne | Information Disclosure | Low | 2019-08-07 | – | 34 |
| All user password hash can be seen from admin panelAnalysed#1489892 | Valid | UPchieve | Information Disclosure | Medium | 2022-06-11 | – | 16 |
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.