Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Unsufficent input verification leads to DoS and resource consumptionAnalysed#2818147 | Valid | Denial of Service | Low | 2025-02-26 | $300 | 108 |
| Circular based introspetion Query leading to single request denial of service and cost consumption and query cost on api.sorare.com/graphqlAnalysed#2048725 | Valid | No weakness recorded | Medium | 2024-10-17 | – | 57 |
| Mystery with a leaked token and Reusability of email confirmation link leading to Account TakeoverAnalysed#1817214 | Valid | Cryptography | Low | 2023-02-03 | $300 | 49 |
| Operation CreateOrUpdateSo5LineupMutation does not restrict multiple captainsAnalysed#2067247 | Valid | Input Validation and Logic | Low | 2023-08-01 | $300 | 23 |
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.