Skip to content

Bug bounty reports15,219

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

Program:LinkedIn
Status
Severity
Weakness
Year:2022
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account5
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
The software does not implement sufficient measures to prevent multiple failed authentication attempts within in a short time frame, making it more su#1591504N/AAuthenticationMedium2022-06-15–3
Rate limit Bypass on contact-us through IP Rotator (burp extension)(https://www.linkedin.com/help/linkedin/solve/contact)#1578121N/ANo weakness recorded–2022-06-15–7
Add me email address Authentication bypass#1607645InformativeNo weakness recorded–2022-07-15–8
Campaign Account Balance and History Disclosed in API ResponseAnalysed#1587374ValidInsecure Direct Object ReferenceMedium2022-11-30–21
Privilege Escalation - "Analyst" Role Can View Email Domains of a Company - [GET /voyager/api/voyagerOrganizationDashEmailDomainMappings]Analysed#1572591ValidAccess ControlMedium2022-08-26–48
IDOR - Delete technical skill assessment result & Gained Badges result of any userAnalysed#1592587ValidNo weakness recordedMedium2022-10-05–48
Can access the job name, creator name and can report any draft/under review/rejected jobAnalysed#1581528ValidInsecure Direct Object ReferenceMedium2022-07-20–65
Unauthorized access to resumes stored on LinkedInAnalysed#1777095ValidInsecure Direct Object ReferenceHigh2022-12-07–112

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.