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
Bounty paid53
Access stated
Access needed
Technique
Clear filters133 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
URL redirection flaw#2622ValidOpen Redirect–2014-08-30–5
Trick make all fixed open redirect links vulnerable again#104087ValidOpen Redirect–2016-05-22$1,0004
Executing scripts on slack-files.com using SVG#100565ValidCross-site Scripting–2016-02-18–4
Stored XSS in Slack (weird, trial and error)#96337ValidCross-site Scripting–2015-11-10–4
Content Spoofing all Integrations in https://team.slack.com/services/new/#22093ValidMisconfiguration and Insecure Design–2014-09-03$2004
Stored XSS#2926ValidCross-site Scripting–2014-04-06–4
Reflected Xss#2777ValidCross-site Scripting–2014-05-19$5004
csrf#2635ValidCross-Site Request Forgery–2014-04-06–4
Stored XSS in username.slack.com#2625ValidCross-site Scripting–2014-08-07–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
Duplicate of #4550#4638ValidNo weakness recorded–2014-05-21–3
User impersonation is possible with incoming webhooks#3722InformativeMisconfiguration and Insecure Design–2014-04-10–3
Content Spoofing#2979InformativeMisconfiguration and Insecure Design–2014-08-11–3
Stored XSS in Channel Chat#2652ValidCross-site Scripting–2014-05-21–3
CSRF on add comment section#2638ValidCross-Site Request Forgery–2014-04-12–3
Unauthenticated Access to some old file thumbnails#145621InformativeAuthentication–2016-06-21–2
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
HTTP Strict Transport Policy not enabled on newly made accounts#26763ValidMisconfiguration and Insecure Design–2014-10-03–2
Content spoofing at Stripe Integrations#21248ValidMisconfiguration and Insecure Design–2014-08-25$1002
Stored XSS in slack.com (integrations)#10297ValidCross-site Scripting–2014-05-29–2
open redirect in https://slack.com#6035InformativeOpen Redirect–2014-05-31–2
TLS1/SSLv3 Renegotiation Vulnerability#5617InformativeNo weakness recorded–2014-08-14–2
Open Redirect in Slack#4549InformativeOpen Redirect–2014-05-21–2
flash content type sniff vulnerability in api.slack.com#3455ValidCross-Site Request Forgery–2014-04-08–2
Deleting Teams implemenation#2975InformativeAuthentication–2014-08-21–2
an xss issue in https://hunter22.slack.com/help/requests/793043#116419ValidCross-site Scripting–2016-04-30$1001
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.