Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SSRF In Get Video ContentsAnalysed#643622 | Valid | Server-Side Request Forgery | Medium | 2019-08-19 | – | 125 |
| SSRF and LFI in site-audit toolAnalysed#794099 | Valid | Server-Side Request Forgery | High | 2020-04-30 | – | 86 |
| Lack of sanitization of the billing address in pdf invoiceAnalysed#2077985 | Valid | Server-Side Request Forgery | High | 2024-03-06 | – | 66 |
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 (4,182 analysed so far), which can be wrong. Data as of 2026-11-15.