Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Email verification bypass via request to endpoint "accounts.insightly.com/signup/provisionuser"Analysed#2718253 | Valid | Access Control | Critical | 2025-08-18 | – | 148 |
| Stored XSS via LINK Name.Analysed#1392262 | Valid | Cross-site Scripting | High | 2025-09-23 | – | 107 |
| Stored XSS in Email NotifcationAnalysed#1597271 | Valid | Cross-site Scripting | Medium | 2025-09-19 | – | 101 |
| returnUrl= allow attacker to redirect users to the another phising website and takeover credientialsAnalysed#1544236 | Valid | Authentication | Medium | 2025-06-04 | – | 94 |
| CSRF vulnerability allows disabling Gmail contacts link for user referralsAnalysed#1668489 | Valid | Cross-Site Request Forgery | Medium | 2025-09-19 | – | 70 |
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,182 analysed so far), which can be wrong. Data as of 2026-11-15.