Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Account takeover at https://try.discourse.org due to no CSRF protection in connecting Yahoo accountAnalysed#423022 | Valid | Cross-Site Request Forgery | High | 2018-12-06 | – | 89 |
| CSRF-tokens on pages without no-cache headers, resulting in ATO when using CloudFlare proxy (Web Cache Deception)Analysed#260697 | Valid | Cross-Site Request Forgery | Low | 2018-08-08 | – | 58 |
| Web Cache Deception Attack (XSS)Analysed#394016 | Valid | Cross-site Scripting | High | 2018-11-18 | $256 | 51 |
| Stored XSS in "post last edited" optionAnalysed#333507 | Valid | Cross-site Scripting | High | 2018-07-09 | $256 | 19 |
| Gaining access to private topics using quoting featureAnalysed#312647 | Valid | Access Control | High | 2018-03-17 | $256 | 19 |
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.