Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Getting New Invitations without Leaving ProgramsAnalysed#999789 | Valid | Input Validation and Logic | Low | 2020-10-15 | – | 322 |
| HTTP Parameter Pollution using semicolons in iframe element at hackerone.com/careers allows loading external Greenhouse formsAnalysed#298265 | Valid | No weakness recorded | None | 2018-03-13 | – | 65 |
| Parameter pollution in social sharing buttonsAnalysed#105953 | Valid | Misconfiguration and Insecure Design | – | 2015-12-19 | $500 | 62 |
| Query parameter reordering causes redirect page to render unsafe URLAnalysed#293689 | Valid | Cross-site Scripting | Medium | 2017-11-30 | $1,500 | 61 |
| GraphQL node interface for ActiveResource models lacks encoding for resource identifier, enabling parameter injection in Payments backendAnalysed#800231 | Valid | Information Disclosure | Medium | 2020-05-11 | – | 42 |
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.