Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| 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 in the https://market.semrush.com/Analysed#837400 | Valid | Access Control | Critical | 2020-04-30 | – | 173 |
| OAuth `redirect_uri` bypass using IDN homograph attack resulting in user's access token leakageAnalysed#861940 | Valid | Information Disclosure | Medium | 2020-06-18 | – | 265 |
| An attacker can buy marketplace articles for lower prices as it allows for negative quantity values leading to business lossAnalysed#771694 | Valid | Input Validation and Logic | High | 2020-04-02 | – | 267 |
| Github information leakedAnalysed#676212 | Valid | Information Disclosure | High | 2019-09-25 | – | 344 |
| Remote Code Execution on www.semrush.com/my_reports on Logo uploadAnalysed#403417 | Valid | Command and Code Injection | Critical | 2019-06-24 | – | 824 |
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,686 analysed so far), which can be wrong. Data as of 2026-11-15.