Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Can register any mobile number in MFA without current code.Analysed#667740 | Valid | Access Control | Low | 2019-08-15 | – | 15 |
| Emails from Grammarly missing sanitization(lack of validation?) -> HTML injection in emails#404864 | Duplicate | Misconfiguration and Insecure Design | Low | 2019-04-30 | – | 22 |
| "More on Wikipedia" link disclose "Referrer" and leak `window.opener` reference for arbitrary websitesAnalysed#409518 | Valid | Misconfiguration and Insecure Design | Low | 2019-04-30 | – | 29 |
| DOM based CSS Injection on grammarly.comAnalysed#500436 | Valid | Cross-site Scripting | Low | 2019-05-06 | $250 | 63 |
| Grammarly Keyboard for Android <4.1 leaks user input through logs (except for sensitive input fields)Analysed#462416 | Valid | Information Disclosure | Low | 2019-06-03 | – | 84 |
| Unauthenticated users can access all food.grammarly.io user's dataAnalysed#745495 | Valid | Access Control | Low | 2020-08-10 | – | 138 |
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.