Skip to content

Bug bounty reports15,219

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

Program:Uber
Status:Valid
Clear
Severity
Weakness:Cross-Site Request Forgery
Clear
Year
Bounty paid4
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Changing paymentProfileUuid when booking a trip allows free ridesAnalysed#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.Analysed#201326ValidCross-Site Request ForgeryCritical2023-03-23$2,00050
Site-wide CSRF on eats.uber.comAnalysed#161529ValidCross-Site Request ForgeryHigh2018-12-19–30
Outdated Wordpress installation and plugins at www.uberxgermany.com create CSRF and XSS vulnerabilitiesAnalysed#323899ValidCross-Site Request ForgeryMedium2021-02-25$50029
Chained vulnerabilities create DOS attack against users on desafio5estrelas.com#624645ValidCross-Site Request ForgeryLow2021-03-30$1,00017
Lack of CSRF protection on uberps.com makes every form vulnerable to CSRF#343120ValidCross-Site Request ForgeryMedium2021-03-15$50015
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 (4,614 analysed so far), which can be wrong. Data as of 2026-11-15.