Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| critical server misconfiguration lead to access to any user sensitive data which include user email and passwordAnalysed#1365738 | Valid | Input Validation and Logic | Medium | 2021-11-02 | $500 | 116 |
| CSRF in Account Deletion feature (https://www.flickr.com/account/delete)Analysed#615448 | Valid | Cross-Site Request Forgery | High | 2021-09-14 | – | 92 |
| High resource consumption by insufficient sanitization of forum threads paginationAnalysed#1916400 | Valid | Denial of Service | Medium | 2025-11-24 | $479 | 75 |
| Incorrect Deep-link validation leading to unresponsive application and deviceAnalysed#1157795 | Valid | Input Validation and Logic | Medium | 2024-07-06 | – | 64 |
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 (3,187 analysed so far), which can be wrong. Data as of 2026-11-15.