Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Discoverability by phone number/email restriction bypassAnalysed#1439026 | Valid | Access Control | High | 2022-02-11 | $5,040 | 217 |
| Twitter ID exposure via error-based side-channel attackAnalysed#505424 | Valid | Information Disclosure | Medium | 2019-05-16 | $1,470 | 154 |
| Protected tweets exposure through the URLAnalysed#491473 | Valid | Information Disclosure | High | 2019-04-19 | $560 | 67 |
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 (2,699 analysed so far), which can be wrong. Data as of 2026-11-15.