Skip to content

Bug bounty reports15,219

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

Program:Snapchat
Status
Severity:Medium
Clear
Weakness
Year
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Intent Leads To Unauthorised Video Call Initiation Leaking Surrounding Informations Of VictimAnalysed#2139260ValidInformation DisclosureMedium2024-04-05–127
RCE/LFI on test Jenkins instance due to improper authentication flowAnalysed#258117ValidAccess ControlMedium2017-08-19–118
Bitmoji source code is accessibleAnalysed#301812ValidInformation DisclosureMedium2021-07-31$1,00092
CreatorID leaked from public content posted to SnapMapsAnalysed#867521ValidServer-Side Request ForgeryMedium2020-12-18$1,00049
Bypass Rate Limits on app.snapchat.com API Endpoint via X-Forwarded-For HeaderAnalysed#727487ValidInput Validation and LogicMedium2021-08-04–40
Subdomain Takeover via Unclaimed WordPress siteAnalysed#274336ValidAuthenticationMedium2017-10-06–39
CRLF Injection at vpn.bitstrips.comAnalysed#237357ValidInjection and SmugglingMedium2017-06-15–24
[spectacles.com] Bypassing quantity limit in ordersAnalysed#246803ValidInjection and SmugglingMedium2017-08-12$25022
RTLO char allowed in chat#196222ValidMisconfiguration and Insecure DesignMedium2017-02-28–18

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