Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Lack of sanitization of the billing address in pdf invoiceAnalysed#2077985 | Valid | Server-Side Request Forgery | High | 2024-03-06 | – | 66 |
| Stored XSS in '' Section and WAF BypassAnalysed#382625 | Valid | Cross-site Scripting | Medium | 2018-12-07 | – | 50 |
| Error Page Content Spoofing or Text InjectionAnalysed#327671 | Valid | Misconfiguration and Insecure Design | Low | 2018-06-29 | – | 33 |
| Code injection in https://www.semrush.comAnalysed#723707 | Valid | Command and Code Injection | Medium | 2019-11-01 | – | 22 |
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.