Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Uber
Status
Severity
Weakness:Cross-Site Request Forgery
Clear
Year
Bounty paid4
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Changing paymentProfileUuid when booking a trip allows free rides#162809ValidCross-Site Request Forgery–2016-09-15–73
[uchat.uberinternals.com] Mattermost doesn't check Origin in Websockets, which leads to the Critical Inforamation Leakage.#201326ValidCross-Site Request Forgery–2023-03-23$2,00050
Attacker could setup reminder remotely using brute force#158393N/ACross-Site Request Forgery–2016-09-19–36
Site-wide CSRF on eats.uber.com#161529ValidCross-Site Request Forgery–2018-12-19–30
Outdated Wordpress installation and plugins at www.uberxgermany.com create CSRF and XSS vulnerabilities#323899ValidCross-Site Request Forgery–2021-02-25$50029
Chained vulnerabilities create DOS attack against users on desafio5estrelas.com#624645ValidCross-Site Request Forgery–2021-03-30$1,00017
Lack of CSRF protection on uberps.com makes every form vulnerable to CSRF#343120ValidCross-Site Request Forgery–2021-03-15$50015
Newsroom.uber HTML form without CSRF protection#144147InformativeCross-Site Request Forgery–2016-07-07–3
CSRF on eng.uber.com may lead to server-side compromise#125594ValidCross-Site Request Forgery–2016-04-26–3

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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in