Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| IDOR in the https://market.semrush.com/Analysed#837400 | Valid | Access Control | Critical | 2020-04-30 | – | 173 |
| Unrestricted file upload in www.semrush.com > /my_reports/api/v1/upload/imageAnalysed#748903 | Valid | Misconfiguration and Insecure Design | Medium | 2020-01-10 | – | 133 |
| IDOR allowing to read another user's token on the Social Media Ads serviceAnalysed#1464168 | Valid | Access Control | High | 2022-08-16 | – | 104 |
| IDOR vulnerability reveals additional informationAnalysed#1770858 | Valid | Insecure Direct Object Reference | Critical | 2024-03-07 | – | 99 |
| SSRF and LFI in site-audit toolAnalysed#794099 | Valid | Server-Side Request Forgery | High | 2020-04-30 | – | 86 |
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 (2,190 analysed so far), which can be wrong. Data as of 2026-11-15.