Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Insecure Direct Object Reference on API without API key#284963 | Informative | No weakness recorded | High | 2018-03-13 | – | 4 |
| clickjacking to Semrush auth login#318295 | Informative | Misconfiguration and Insecure Design | None | 2018-03-13 | – | 2 |
| SSLv3 Poodle Attack on Ip Of semrush#318594 | N/A | Misconfiguration and Insecure Design | Low | 2018-03-13 | – | 1 |
| Security misconfiguration "weak passwords".#285482 | Informative | Misconfiguration and Insecure Design | Medium | 2018-03-13 | – | 1 |
| Email Spoofing#276614 | Duplicate | Misconfiguration and Insecure Design | Medium | 2018-03-13 | – | 1 |
| Ports are not shown in third-party site redirect warning page.#482170 | Duplicate | No weakness recorded | Low | 2019-04-12 | – | – |
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,187 analysed so far), which can be wrong. Data as of 2026-11-15.