Skip to content

Bug bounty reports15,219

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

Program:HackerOne
Status
Severity
Weakness
Year
Bounty paid3
Access stated:A user account
Access needed
  • No account0
  • A user account5
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Invited team member can disclosure slack channels#509574ValidInformation DisclosureLow2019-04-05$50016
Read-only team members can read all properties of webhooks#818848ValidAccess ControlLow2020-04-29–30
Organization members can delete reports in teams they have no access to#2203432ValidAccess ControlMedium2023-11-22–57
Reporter, external users, collaborators can mark sent swag awarded to reporter as unsentAnalysed#717729ValidInsecure Direct Object ReferenceMedium2019-10-25–76
Triager/Team members can edit hacker's report and hacker is not even notifiedAnalysed#2061367ValidNo weakness recordedMedium2023-08-31$2,50084
Program Member Could Duplicate Report To A Non Related Program Original ReportAnalysed#2513082ValidAccess ControlHigh2024-06-19–104
[ Spot Check ] Team members can edit a user's write-upAnalysed#2530242ValidAccess ControlLow2024-06-06–149
adding h1_analyst_* to username for normal usersAnalysed#1770797ValidInput Validation and LogicLow2023-04-12$500187

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

Updated AboutDevelopersSign in