Lark Technologies · disclosed reports
Access Control
16 disclosed reports · $0 paid · 16 valid
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. A report opens its page here: our analysis where there is one, and the link to HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
Open Lark Technologies on HackerOne- reports
- 16
- valid
- 16
- paid a bounty
- 0
Every one of the 16 is a mark on the map. Named now: 1 to 16, most upvoted first.
- Attacker is able to join any tenant on larksuite and view personal files/chats.
- Non privileged user is able to approve his own app himself leading to mass privilege escalations.
- Sensitive information of helpdesk is being leaked.
- Accessing/Editing Folders of Other Users in the Orginisation.
- Improper Access Control allows OTP bypass
- Improper Access Control on Lark Footer Feature
- Privilege Escalation to All-staff group
- Users Without Permission Can Download Restricted Files
- Normal User is able to EXPORT Feature Usage Statistics
- Access to private file's of helpdesk.
- User with single department permission can view applicant list of all department's
- Removed user can still view comments on the file/documents.
- Ability to View Non-Permitted Admin Log
- Viewer is able to leak the previous versions of the file
- IDOR Allows Viewer to Delete Bin's Files
- Sub-Dept User Can Add User's To Main Department.
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-14. CVE List through 2026-11-14 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-14. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data. Use this via MCP