Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| XSS At "pages.et.uber.com"#156098 | N/A | Cross-site Scripting | – | 2016-08-19 | – | 267 |
| Attacker could setup reminder remotely using brute force#158393 | N/A | Cross-Site Request Forgery | – | 2016-09-19 | – | 36 |
| Session not expired When logout [partners.uber.com]#231041 | N/A | No weakness recorded | None | 2017-05-26 | – | 12 |
| Content injection on 404 error page at faspex.uber.com#155685 | N/A | Misconfiguration and Insecure Design | – | 2016-08-12 | – | 5 |
| reopen #128853 (Information disclosure at lite.uber.com)#129712 | N/A | Information Disclosure | – | 2016-07-26 | – | 5 |
| Uber is Flooding my Mobile with SMS Daily like a cron JOB#141339 | N/A | Misconfiguration and Insecure Design | – | 2016-07-25 | – | 4 |
| Privilege escalation to allow non activated users to login and use uber partner ios app#126260 | N/A | Access Control | – | 2016-06-13 | – | 1 |
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.