Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Web cache deception attack - expose earning state information#439021 | Informative | Access Control | Low | 2019-04-12 | – | 10 |
| subdomain takeover at news-static.semrush.comAnalysed#294201 | Valid | Access Control | High | 2018-01-10 | – | 40 |
| CORS misconfiguration which leads to the disclosure of certain data concerning the user.Analysed#769058 | Valid | Access Control | Low | 2020-02-15 | – | 46 |
| Critically Sensitive Spring Boot Endpoints ExposedAnalysed#1022048 | Valid | Access Control | Critical | 2022-02-10 | – | 59 |
| IDOR allowing to read another user's token on the Social Media Ads serviceAnalysed#1464168 | Valid | Access Control | High | 2022-08-16 | – | 104 |
| IDOR in the https://market.semrush.com/Analysed#837400 | Valid | Access Control | Critical | 2020-04-30 | – | 173 |
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.