Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Attacker can unpin posts from companies he's not part of.Analysed#1862677 | Valid | No weakness recorded | Low | 2023-05-12 | – | 20 |
| HTML injection at Company Name or Product Name and can be shown on Contact Sales formAnalysed#2076019 | Valid | No weakness recorded | Low | 2023-10-18 | – | 32 |
| Html injection in event DescriptionAnalysed#2215418 | Valid | Input Validation and Logic | Low | 2024-01-29 | – | 55 |
| User Details Can Be Disclosed Even If The Account IS In Hibernation StateAnalysed#1728087 | Valid | Information Disclosure | Low | 2023-12-06 | – | 57 |
| HTML Injection in LinkedIn Premium Support ChatAnalysed#3079966 | Valid | No weakness recorded | Low | 2025-05-07 | – | 102 |
| Previous commentor on post can still comment even after comment permission is changed to disabledAnalysed#3151001 | Valid | Access Control | Low | 2026-02-03 | – | 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.