Skip to content

Bug bounty reports15,219

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

Program:Vimeo
Status
Severity
Weakness
Year:2016
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account2
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters11 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Legacy API exposes private video titles#111386ValidInformation Disclosure–2016-02-10–1
No Limitation on Following allows user to follow people automatically!#43846ValidCross-Site Request Forgery–2016-05-02–2
Private, embeddable videos leaks data through Facebook & Open Graph#121919ValidInformation Disclosure–2016-05-21–3
Missing rate limit on private videos password#124564ValidAccess Control–2016-03-22–3
XSS in Subtitles of Vimeo Flash Player and Hubnut#137023DuplicateCross-site Scripting–2016-09-14–4
Invite any user to your group without even following him#52707ValidAccess Control–2016-08-25–6
Error page Text Injection.#130914DuplicateMisconfiguration and Insecure Design–2016-08-02–6
[vimeopro.com] CRLF Injection#39181ValidNo weakness recorded–2016-10-24–10
CSRF on Vimeo via cross site flashing leading to info disclosure and private videos go public#136481ValidCross-Site Request Forgery–2016-07-29–15
All Vimeo Private videos disclosure via Authorization BypassAnalysed#137502ValidInformation Disclosure–2016-07-29–35
Downloading password protected / restricted videosAnalysed#145467ValidNo weakness recorded–2016-09-05–43

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.