Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Unrestricted access to any "connected pack" on docsAnalysed#777942 | Valid | Access Control | Medium | 2020-04-14 | – | 27 |
| Grammarly Keyboard for Android "Authorization Code with PKCE" flow implementation vulnerability that allows account takeoverAnalysed#824931 | Valid | Cryptography | Medium | 2020-07-24 | – | 76 |
| Use Github pack with Coda employee github account (search code of Coda's private repositories)Analysed#676581 | Valid | No weakness recorded | Medium | 2020-01-02 | – | 104 |
| Lack or Origin check leads to Cross-Site Websocket Hijacking (CSWSH)Analysed#535436 | Valid | Access Control | High | 2020-01-04 | $800 | 134 |
| 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.