Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Server Side Request Forgery (SSRF) via Analytics ReportsAnalysed#2262382 | Valid | Server-Side Request Forgery | Critical | 2023-12-08 | $25,000 | 529 |
| Blind SSRF on errors.hackerone.net due to Sentry misconfigurationAnalysed#374737 | Valid | Server-Side Request Forgery | Low | 2018-07-04 | $3,500 | 143 |
| Server Side Request Forgery (SSRF) in webhook functionalityAnalysed#2301565 | Valid | Server-Side Request Forgery | Medium | 2024-01-30 | $2,500 | 140 |
| Deprecated Hacker101 coursework repository mentions Heroku App that is susceptible to takeoverAnalysed#514451 | Valid | Server-Side Request Forgery | None | 2019-04-04 | $500 | 68 |
| Upload profile photo from URL#713 | Valid | Server-Side Request Forgery | – | 2014-02-15 | – | 44 |
| Blind SSRF in "Integrations" by abusing a bug in Ruby's native resolver.#287245 | Valid | Server-Side Request Forgery | – | 2017-11-09 | – | 30 |
| Lack of input sanitization in Marketo form leads to execution of HTML in lead emails#220009 | Valid | Server-Side Request Forgery | – | 2017-10-03 | $500 | 25 |
| Additional bypass allows SSRF for internal netblocks#288950 | Valid | Server-Side Request Forgery | – | 2017-11-16 | – | 20 |
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 (1,932 analysed so far), which can be wrong. Data as of 2026-11-15.