Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF in github integrationAnalysed#174328 | Valid | Cross-Site Request Forgery | Medium | 2016-11-18 | $500 | 22 |
| CSRF - Add optional two factor mobile number#155774 | Valid | Cross-Site Request Forgery | – | 2016-08-17 | $500 | 7 |
| State parameter missing on google OAuth#2688 | Valid | Cross-Site Request Forgery | – | 2014-04-06 | – | 6 |
| CSRF vulnerability on https://sehacure.slack.com/account/settings#2628 | Valid | Cross-Site Request Forgery | – | 2014-07-26 | – | 5 |
| csrf#2635 | Valid | Cross-Site Request Forgery | – | 2014-04-06 | – | 4 |
| CSRF on add comment section#2638 | Valid | Cross-Site Request Forgery | – | 2014-04-12 | – | 3 |
| Logout any user of same team#54610 | Valid | Cross-Site Request Forgery | – | 2015-05-05 | – | 2 |
| flash content type sniff vulnerability in api.slack.com#3455 | Valid | Cross-Site Request Forgery | – | 2014-04-08 | – | 2 |
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.