Skip to content

Bug bounty reports15,219

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

Program:Snapchat
Status
Severity
Weakness
Year:2016
Clear
Bounty paid2
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account3
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters6 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Subdomain takeover in http://support.scan.me pointing to Zendesk (a Snapchat acquisition)#114134ValidCross-site Scripting–2016-02-16–14
Subdomain takeover of blog.snapchat.com#171942ValidNo weakness recorded–2016-10-05–14
Bypassing "You've requested your data the maximum number of times today." + "Please Verify an email address with snapchat to continue"#173043ValidAuthentication–2016-11-25–20
Incoming email hijacking on sc-cdn.netAnalysed#168476ValidMisconfiguration and Insecure Design–2016-09-23–25
Administrator access to a Django Administration Panel on *.sc-corp.net via bruteforced credentialsAnalysed#128114ValidAuthentication–2016-07-14$1,00054
Subdomain takeover on http://fastly.sc-cdn.net/Analysed#154425ValidMisconfiguration and Insecure Design–2016-08-22$3,000114

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