Skip to content

Bug bounty reports15,219

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

Program:FetLife
Status:Valid
Clear
Severity
Weakness
Year
Bounty paid1
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Race condition in endpoint POST fetlife.com/users/invitation, allow attacker to generate unlimited invitesAnalysed#1460373ValidNo weakness recordedMedium2022-03-09–30
Able to detect if a user is FetLife supporter although this user hides their support badge in fetlife.com/conversations/{id} JSON responseAnalysed#1423704ValidInformation DisclosureMedium2022-02-11–34
Specific Payload makes a Users Posts unavailableAnalysed#1176794ValidDenial of ServiceMedium2022-01-26$10049
Able to see location coordinates in any event without permission to do soAnalysed#2610467ValidInformation DisclosureLow2024-09-25–62
Able to access private picture/video/writing when requesting for their JSON responseAnalysed#1424291ValidInformation DisclosureMedium2021-12-16–73
Stored XSS via Angular Expression injection via Subject while starting conversation with other users.Analysed#1095934ValidCross-site ScriptingMedium2021-03-07–82
Stored XSS via `Create a Fetish` section.Analysed#1085914ValidCross-site ScriptingMedium2021-02-25–98
Google API key leaked to PublicAnalysed#1065041ValidInformation DisclosureLow2021-01-23–228

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.