Skip to content

Bug bounty reports15,219

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

Program:Slack
Status
Severity
Weakness:Cross-site Scripting
Clear
Year
Bounty paid12
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters32 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
an xss issue in https://hunter22.slack.com/help/requests/793043#116419ValidCross-site Scripting–2016-04-30$1001
Stored XSS in slack.com (integrations)#10297ValidCross-site Scripting–2014-05-29–2
Self-XSS in posts by formatting text as code#89505ValidCross-site Scripting–2015-11-10–2
Reflected Self-XSS in Slack#97683ValidCross-site Scripting–2015-11-10–2
Stored XSS in Channel Chat#2652ValidCross-site Scripting–2014-05-21–3
Reflective XSS can be triggered in IE#2497ValidCross-site Scripting–2015-03-15$1504
Stored XSS in username.slack.com#2625ValidCross-site Scripting–2014-08-07–4
Reflected Xss#2777ValidCross-site Scripting–2014-05-19$5004
Stored XSS#2926ValidCross-site Scripting–2014-04-06–4
Stored XSS in Slack (weird, trial and error)#96337ValidCross-site Scripting–2015-11-10–4
Executing scripts on slack-files.com using SVG#100565ValidCross-site Scripting–2016-02-18–4
Stored XSS in Slack.com#6002ValidCross-site Scripting–2015-03-09–5
Stored XSS on this link https://sehacure.slack.com/help/requests/#2639ValidCross-site Scripting–2014-08-30–6
a stored xss in slack integration https://onerror.slack.com/services/import#33018ValidCross-site Scripting–2016-05-22$5006
Stored XSS in www.slack-files.com#2617ValidCross-site Scripting–2014-05-23–8
Stored XSS in Slackbot Direct Messages#4561ValidCross-site Scripting–2014-05-04–8
"a stored xss issue in share post menu"#148848ValidCross-site Scripting–2017-06-25$5008
Stored XSS Found#9774ValidCross-site Scripting–2014-06-01–9
a stored xss issue in https://files.slack.com#149011ValidCross-site Scripting–2017-06-25$5009
Open Redirect on slack.com#140447ValidCross-site Scripting–2016-10-02$50012
dom xss in https://www.slackatwork.com#196624ValidCross-site ScriptingLow2017-03-02–13
Bypass to postMessage origin validation via FTP#210654ValidCross-site ScriptingHigh2017-04-21–15
Stored XSS in files.slack.comAnalysed#827606ValidCross-site ScriptingMedium2021-12-02–19
Subdomain takeover on podcasts.slack-core.comAnalysed#195350ValidCross-site ScriptingLow2017-01-04$10027
Stored XSS(Cross Site Scripting) In Slack App NameAnalysed#159460ValidCross-site Scripting–2016-11-22$1,00029
Store XSSAnalysed#187410ValidCross-site ScriptingHigh2017-01-01–44
XSS on link and window.openerAnalysed#834071ValidCross-site ScriptingMedium2023-01-23$1,00049
The Custom Emoji Page has a Reflected XSSAnalysed#258198ValidCross-site ScriptingHigh2017-09-24–56
Stored XSS through PDF viewerAnalysed#881557ValidCross-site ScriptingHigh2022-03-16$4,87576
Stored XSS on team.slack.com using new Markdown editor of posts inside the Editing mode and using javascript-URIsAnalysed#132104ValidCross-site Scripting–2016-09-01–103
XSS in gist integrationAnalysed#11073ValidCross-site Scripting–2019-04-28$500157
XSS vulnerable parameter in a location hashAnalysed#146336ValidCross-site Scripting–2019-10-16–455

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