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:2018
Clear
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:Not clear from the report
Technique
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Markdown parsing issue enables insertion of malicious tags and event handlersAnalysed#299728ValidCross-site ScriptingHigh2018-01-29$5,000184
Team object in GraphQL discloses team group names and permissionsAnalysed#343464ValidInformation DisclosureMedium2018-05-04$2,50075
The request tells the number of private programs, the new system of authorization /invite/tokenAnalysed#310946ValidInformation DisclosureMedium2018-02-14$2,00071
TeamProfile exposes partially sensitive information through GraphQLAnalysed#389600ValidInformation DisclosureLow2018-08-08–60
Team object in GraphQL that have a published external program may expose existence of a private programAnalysed#347937ValidInformation DisclosureNone2018-07-04–39
Internal usage of AdBlockPlus may expose PoC URLs to unknown third-partiesAnalysed#395518ValidInformation DisclosureLow2018-08-17–32
Unicorn worker pool exhaustion by continuously updating payout preferencesAnalysed#317543ValidDenial of ServiceMedium2018-03-30–25

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.