Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Previously created sessions continue being valid after MFA activationAnalysed#667739 | Valid | Access Control | Medium | 2019-08-19 | – | 176 |
| Unauthenticated users can access all food.grammarly.io user's dataAnalysed#745495 | Valid | Access Control | Low | 2020-08-10 | – | 138 |
| 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 |
| Unrestricted access to any "connected pack" on docsAnalysed#777942 | Valid | Access Control | Medium | 2020-04-14 | – | 27 |
| Can register any mobile number in MFA without current code.Analysed#667740 | Valid | Access Control | Low | 2019-08-15 | – | 15 |
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.