Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Handling of `tracking` command allows making arbitrary blind requests with user's cookies from Grammarly Extension's originAnalysed#389108 | Valid | No weakness recorded | Critical | 2019-08-01 | – | 202 |
| Lack of CSRF header validation at https://g-mail.grammarly.com/profileAnalysed#629892 | Valid | Information Disclosure | Medium | 2019-10-31 | – | 140 |
| Lack or Origin check leads to Cross-Site Websocket Hijacking (CSWSH)Analysed#535436 | Valid | Access Control | High | 2020-01-04 | $800 | 134 |
| Permissive CORS policy trusting arbitrary extensions originAnalysed#412490 | Valid | Access Control | Medium | 2019-11-06 | $500 | 33 |
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, where there is one, which can be wrong. Data as of 2026-11-15.