Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Denial of Service (DoS) Vulnerability in Drafts Creation EndpointAnalysed#3400140 | Valid | Denial of Service | High | 2026-06-30 | $1,024 | 98 |
| 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 |
| Application Level DoS - Large Markdown Payload in Reply Section Leading to Resource ExhaustionAnalysed#3058919 | Valid | Denial of Service | High | 2025-10-18 | – | 84 |
| Any user with invite capabilities can take-over any account on DiscourseAnalysed#242765 | Valid | No weakness recorded | Critical | 2017-11-06 | $1,024 | 75 |
| SSRF in upload IMG through URLAnalysed#228377 | Valid | Information Disclosure | Low | 2017-06-18 | $64 | 32 |
| Hidden/restricted tags can be mutated through synonym ID paths without per-tag authorizationAnalysed#3689633 | Valid | Insecure Direct Object Reference | Medium | 2026-08-26 | – | 31 |
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 (3,437 analysed so far), which can be wrong. Data as of 2026-11-15.