Skip to content

Bug bounty reports15,219

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

Program:Slack
Status
Severity
Weakness
Year:2015
Clear
Bounty paid5
Access stated
Access needed
  • No account1
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters12 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Facebook Takeover using Slack using 302 from files.slack.com with access_tokenAnalysed#6017ValidOpen Redirect–2015-01-11–17
Stored XSS in Slack.com#6002ValidCross-site Scripting–2015-03-09–5
Stored XSS in Slack (weird, trial and error)#96337ValidCross-site Scripting–2015-11-10–4
Reflective XSS can be triggered in IE#2497ValidCross-site Scripting–2015-03-15$1504
Team admin can add billing contacts#47940ValidAccess Control–2015-04-03$2003
Team admin can change unauthorized team setting (allow_message_deletion)#46750ValidAccess Control–2015-05-30$1003
Team admin can change unauthorized team setting (require_at_for_mention)#46747ValidAccess Control–2015-04-30$2003
Reflected Self-XSS in Slack#97683ValidCross-site Scripting–2015-11-10–2
Self-XSS in posts by formatting text as code#89505ValidCross-site Scripting–2015-11-10–2
Logout any user of same team#54610ValidCross-Site Request Forgery–2015-05-05–2
File upload XSS (Java applet) on http://slackatwork.com/#97657ValidCommand and Code Injection–2015-11-11$2001
Link vulnerability leads to phishing attacks#66994InformativeNo weakness recorded–2015-07-13–1

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.