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:2014
Clear
Bounty paid4
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters35 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Open redirect vulnerability#2731InformativeOpen Redirect–2014-04-06–11
Slack OAuth2 "redirect_uri" Bypass#2575ValidAuthentication–2014-05-29–10
Stored XSS Found#9774ValidCross-site Scripting–2014-06-01–9
Data exports stored on S3 can be scraped easily#2746ValidAuthentication–2014-12-09–9
Open Redirect login account#16718ValidOpen Redirect–2014-08-25$1008
Stored XSS in Slackbot Direct Messages#4561ValidCross-site Scripting–2014-05-04–8
Email enumeration#2766InformativeInformation Disclosure–2014-04-02–8
Stored XSS in www.slack-files.com#2617ValidCross-site Scripting–2014-05-23–8
Broken Authentication (including Slack OAuth bugs)#2559ValidMisconfiguration and Insecure Design–2014-08-30–8
Remote file Inclusion - RFI in upload#14092InformativeCommand and Code Injection–2014-07-08–7
Session Fixation disclosing email address#2582InformativeInformation Disclosure–2014-03-31–7
State parameter missing on google OAuth#2688ValidCross-Site Request Forgery–2014-04-06–6
Stored XSS on this link https://sehacure.slack.com/help/requests/#2639ValidCross-site Scripting–2014-08-30–6
Password Policy issue (Weak Protect)#17160ValidMisconfiguration and Insecure Design–2014-09-04–5
SSRF on https://whitehataudit.slack.com/account/photo#14127ValidCommand and Code Injection–2014-12-21–5
CSRF vulnerability on https://sehacure.slack.com/account/settings#2628ValidCross-Site Request Forgery–2014-07-26–5
URL redirection flaw#2622ValidOpen Redirect–2014-08-30–5
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
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
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

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.