Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| HTML injection via insecure parameter [https://www.ubercarshare.com/]Analysed#1790444 | Valid | Cross-site Scripting | Medium | 2023-03-23 | – | 35 |
| [data-07.uberinternal.com] SSRF in Portainer app lead to access to Internal Docker API without AuthAnalysed#366638 | Valid | Server-Side Request Forgery | Critical | 2023-03-23 | $500 | 37 |
| DOM based XSS via insecure parameter on [ https://uberpay-mock-psp.uber.com ]Analysed#1767151 | Valid | Cross-site Scripting | Medium | 2023-03-23 | – | 39 |
| [uchat.uberinternals.com] Mattermost doesn't check Origin in Websockets, which leads to the Critical Inforamation Leakage.Analysed#201326 | Valid | Cross-Site Request Forgery | Critical | 2023-03-23 | $2,000 | 50 |
| Complete Admin account takeover due to PhpDebugBar turned on in Uber's production serverAnalysed#1883806 | Valid | Misconfiguration and Insecure Design | Medium | 2023-08-23 | – | 90 |
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.