Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF on signup endpoint (auto-api.yelp.com)#178831 | Valid | Cross-Site Request Forgery | – | 2017-03-01 | – | 13 |
| Clickjacking Vulnerability found on Yelp#214087 | Valid | Cross-Site Request Forgery | Low | 2017-05-12 | – | 13 |
| Information disclosure - emails disclosed in response > staging.seatme.usAnalysed#49170 | Valid | Cross-Site Request Forgery | – | 2017-05-11 | – | 21 |
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.