Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| phpinfo() exposed on ██████████Analysed#2641211 | Valid | Misconfiguration and Insecure Design | Medium | 2024-11-21 | – | 51 |
| subdomain takeover at █████████Analysed#2106886 | Valid | Misconfiguration and Insecure Design | High | 2023-11-15 | – | 40 |
| phpinfo() exposed on ██████████Analysed#2666151 | Valid | Misconfiguration and Insecure Design | – | 2024-11-21 | – | 36 |
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.