Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF to delete a pet on ██████Analysed#2261600 | Valid | Cross-Site Request Forgery | Low | 2024-02-05 | – | 61 |
| CSRF in Delete Pet FunctionAnalysed#2445106 | Valid | Cross-Site Request Forgery | Medium | 2024-11-19 | – | 32 |
| CSRF resulting in adding pet at ███████Analysed#2313478 | Valid | Cross-Site Request Forgery | Low | 2024-06-25 | – | 29 |
| No CSRF protection when adding an item to cartAnalysed#2190062 | Valid | Cross-Site Request Forgery | Low | 2024-01-30 | – | 29 |
| CSRF to delete a petAnalysed#2029753 | Valid | Cross-Site Request Forgery | Medium | 2023-08-30 | – | 25 |
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,935 analysed so far), which can be wrong. Data as of 2026-11-15.