Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Able to steal private files by manipulating response using Auto Reply function of LarkAnalysed#1387320 | Valid | Insecure Direct Object Reference | High | 2022-01-25 | – | 39 |
| Improper Access Control allows OTP bypassAnalysed#1948506 | Valid | Access Control | Medium | 2023-10-25 | – | 40 |
| Accessing/Editing Folders of Other Users in the Orginisation.Analysed#1025881 | Valid | Access Control | High | 2022-10-29 | – | 42 |
| Sensitive information of helpdesk is being leaked.Analysed#805023 | Valid | Access Control | Medium | 2021-03-06 | – | 45 |
| Non privileged user is able to approve his own app himself leading to mass privilege escalations.Analysed#1168475 | Valid | Access Control | High | 2021-11-20 | – | 45 |
| Able to steal private files by manipulating response using Compose Email function of LarkAnalysed#1373784 | Valid | Insecure Direct Object Reference | High | 2022-01-25 | – | 50 |
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 (2,942 analysed so far), which can be wrong. Data as of 2026-11-15.