Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SELECT ... INTO OUTFILE does not enforce the FILE WRITE privilege unprivileged arbitrary file write on the serverAnalysed#3780695 | Valid | Access Control | High | 2026-07-13 | – | 50 |
| Insecure Direct Object Reference (IDOR) allows creating folders.Analysed#3353057 | Valid | Insecure Direct Object Reference | Low | 2026-07-01 | – | 39 |
| Delete any folder for any user within the organizationAnalysed#3353035 | Valid | Insecure Direct Object Reference | Low | 2026-07-01 | – | 35 |
| Exceeding the maximum number of spaces allowed by exploiting a Race Condition in the Workspace creation processAnalysed#3295500 | Valid | Input Validation and Logic | Low | 2026-07-01 | – | 35 |
| Privilege Escalation – Access to the Alert Subscribers page for users with low privilegesAnalysed#3353000 | Valid | Access Control | Low | 2026-07-01 | – | 26 |
| Insufficient checks in the file path parameter allow writing to unauthorized directoriesAnalysed#3384615 | Valid | File and Path Handling | Low | 2026-06-24 | – | 12 |
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.