Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Stored XSS in '' Section and WAF BypassAnalysed#382625 | Valid | Cross-site Scripting | Medium | 2018-12-07 | – | 50 |
| XSS Reflected on my_reportAnalysed#491023 | Valid | Cross-site Scripting | Low | 2019-06-21 | – | 25 |
| Reflected XSS using Header InjectionAnalysed#297203 | Valid | Cross-site Scripting | Low | 2018-01-18 | – | 25 |
| Content Injection on api.semrush.com to Reflected XSS#752042 | Valid | Cross-site Scripting | Low | 2020-04-02 | – | 16 |
| XSS on redirection page( Bypassed)#316319 | Valid | Cross-site Scripting | Low | 2018-06-13 | – | 15 |
| Reflected XSS on https://www.semrush.com/my_reports/externalSource/callback/googleAccountsGMB#786238 | Valid | Cross-site Scripting | Low | 2020-04-02 | – | 12 |
| Post Based XSS On Upload Via CK Editor [semrush.com]#375352 | Valid | Cross-site Scripting | Low | 2018-08-17 | – | 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 (4,182 analysed so far), which can be wrong. Data as of 2026-11-15.