Skip to content

Bug bounty reports15,219

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

Program:Yelp
Status
Severity
Weakness
Year
Bounty paid0
Access stated
Access needed
Technique
Clear filters74 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
RCE on build server via misconfigured pip installAnalysed#946409ValidSupply Chain and Malicious Code–2021-02-09–366
yelp.com XSS ATO (via login keylogger, link Google account)Analysed#2010530ValidCross-site Scripting–2023-08-15–324
I.D.O.R To Order,Book,Buy,reserve On YELP FOR FREE (UNAUTHORIZED USE OF OTHER USER'S CREDIT CARD)Analysed#391092ValidInsecure Direct Object Reference–2020-08-19–214
Object Level access control leads to reading user's full requests, sessions, and error messages#2891449ValidAccess ControlMedium2025-01-18–113
CRITICAL Insecure Direct Object Reference (I.D.O.R) - Link Other User's Credit Card#358143ValidInformation Disclosure–2020-08-19–87
Access to internal CMS containing private Data#100926ValidAuthentication–2016-10-07–83
Unauthorized Reservation Cancellation Through IDOR Vulnerability#2944357DuplicateInsecure Direct Object ReferenceHigh2025-01-29–79
Yelp for Business: locked Email field silently editable via API#3766455ValidInput Validation and LogicMedium2026-07-02–76
Privilege Escalation - A Non Owner User Who Does not Have access to the user management can invite other users to the restaurant page#2396549ValidAccess ControlLow2025-01-29–75
X-Forward-For Header allows to bypass access restrictions#1011767ValidAccess Control–2020-10-26–73
Privilege Escalation - A Low Privilege User who does not have access to the user management module can remove the owner of the business account#2396571ValidAccess ControlLow2025-01-28–60
RXSS AT https://proze.yelp.com/tmsubscribe.net/vidsn.aspx#2947762ValidCross-site ScriptingMedium2025-06-30–56
Debug Deep Link Abuse Allows Repeated Forced Logout and Application Disruption#3829030ValidMisconfiguration and Insecure DesignLow2026-08-13–54
Bybass The Closing of the account and logged again to your account#167489ValidAuthentication–2016-10-21–34
I.D.O.R TO EDIT ALL USER'S CREDIT CARD INFORMATION+(Partial credit card info disclosure)#361984ValidInsecure Direct Object Reference–2020-08-19–32
No rate limiting for confirmation email lead to email flooding#774050ValidMisconfiguration and Insecure Design–2020-02-11–24
Multiple Vulnerabilities in (*.blog.yelp.com) - Leakage user admin Sensitive Exposure#779656InformativeInput Validation and Logic–2020-01-29–23
Able to download arbitrary PHP files at yelpblog.com#194351ValidAccess Control–2017-02-06–21
Information disclosure - emails disclosed in response > staging.seatme.us#49170ValidCross-Site Request Forgery–2017-05-11–21
CORS Misconfiguration on Yelp#1707616InformativeNo weakness recorded–2022-09-28–19
CRITICAL-CLICKJACKING at Yelp Reservations Resulting in exposure of victim Private Data (Email info) + Victim Credit Card MissUse.#355859ValidAccess Control–2020-08-21–18
Password reset token not expiring#170161ValidAuthentication–2017-11-09–18
Direct access to tox.ini file which is contain configuration details#1824865ValidInformation Disclosure–2023-03-02–15
DoS of https://blog.yelp.com/ and other WP instances via CVE-2018-6389#753491InformativeNo weakness recorded–2020-01-17–15
[engineeringblog.yelp.com] CRLF Injection#66391N/ANo weakness recorded–2017-11-09–14
No rate limit on subscribe form#1708824InformativeInput Validation and Logic–2022-10-05–13
Clickjacking Vulnerability found on Yelp#214087ValidCross-Site Request Forgery–2017-05-12–13
CSRF on signup endpoint (auto-api.yelp.com)#178831ValidCross-Site Request Forgery–2017-03-01–13
PURGE is not authenticated#629612InformativeAuthentication–2023-01-19–12
Leaking sensitive information lead to compromise employer API keys#273630ValidInformation Disclosure–2017-11-09–12
IDNs displayed in unicode in messages/about/talk sections (Homograph Attack)#172933ValidMisconfiguration and Insecure Design–2017-11-09–12
Public Github Repo Leaking Internal Credentials#1763266InformativeNo weakness recorded–2022-11-07–10
Robots.txt file with potentially sensitive content.#1724771N/AInformation Disclosure–2023-01-13–10
Verification of email addresses possible through https://www.yelp.com/signup/facebook#194721ValidInformation Disclosure–2017-09-16–10
Verification of E-Mail address possible on https://biz.yelp.com/login and https://biz.yelp.com/forgot#166265ValidInformation Disclosure–2016-10-27–10
Self-XSS via location cookie city field when getting suggestions for a new location#166709InformativeCross-site Scripting–2016-11-30–8
Clickjacking lead to remove review#965141ValidNo weakness recorded–2020-09-01–7
Unauthorized Use of Victim Credit Card#391385ValidInformation Disclosure–2020-08-21–7
Firefly's verify_access_token() function does a byte-by-byte comparison of HMAC values.#240958ValidCryptography–2017-07-10–7
X.509 certificate validation fails on international vanity domains#180538ValidMisconfiguration and Insecure Design–2017-02-06–7
Requesting Show CheckIn Alert for Non Friend User#174882ValidInformation Disclosure–2016-10-27–7
installed.json sensitive file was publicly accessible on your web application which discloses information about authors and admins#1586524InformativeInformation Disclosure–2022-10-22–6
Server-side request forgery (ssrf)#1712240N/AServer-Side Request Forgery–2022-09-28–5
ClickJacking on IMPORTANT Functions of Yelp#305128ValidMisconfiguration and Insecure Design–2020-08-21–5
Ngnix Server version disclosure 404 Page!#167036InformativeInformation Disclosure–2017-11-09–5
IDOR(indirect object references) on add friend,complement and send message#166849N/AMisconfiguration and Insecure Design–2017-11-09–5
Autofill/Autosave password on login#1720621N/AAuthentication–2022-10-11–4
CORS Misconfiguration on trust.yelp.com#1716286N/ANo weakness recorded–2022-10-10–4
xmlrpc file enabled#1575401DuplicateInformation Disclosure–2022-06-16–4
Fraudulent claim of business.#1422227N/ANo weakness recorded–2023-02-06–4

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

Updated AboutDevelopersSign in