Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Stored XSS in developer.uber.comAnalysed#131450 | Valid | Cross-site Scripting | – | 2016-06-27 | $7,500 | 223 |
| uber.com may RCE by Flask Jinja2 Template InjectionAnalysed#125980 | Valid | Command and Code Injection | – | 2016-04-06 | $10,000 | 137 |
| Changing paymentProfileUuid when booking a trip allows free ridesAnalysed#162809 | Valid | Cross-Site Request Forgery | – | 2016-09-15 | – | 73 |
| Multiple vulnerabilities in a WordPress plugin at drive.uber.comAnalysed#135288 | Valid | SQL Injection | – | 2016-08-23 | – | 55 |
| Avoiding Surge PricingAnalysed#125250 | Valid | Misconfiguration and Insecure Design | – | 2016-08-11 | – | 45 |
| Possibility to brute force invite codes in riders.uber.comAnalysed#125505 | Valid | Misconfiguration and Insecure Design | – | 2016-06-13 | $5,000 | 35 |
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.