Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Information Exposure Through Directory Listing#1948562 | Valid | Information Disclosure | High | 2023-06-23 | – | 13 |
| Customer Data Exposure via Insecure Endpoint of couponAnalysed#2828720 | Valid | Information Disclosure | Medium | 2025-05-27 | – | 28 |
| ███████ - Publicly Accessible public_html Directory Exposing WordPress ConfigurationAnalysed#3066548 | Valid | Information Disclosure | Medium | 2026-02-24 | – | 29 |
| Sensitive Information Exposed at █████Analysed#2308654 | Valid | Information Disclosure | High | 2024-01-30 | – | 33 |
| massive PII leakage for ███████Analysed#2887506 | Valid | Information Disclosure | Medium | 2025-05-12 | – | 36 |
| Users Data Exposure via Insecure EndpointAnalysed#2828608 | Valid | Information Disclosure | Medium | 2025-05-12 | – | 40 |
| debug.log leaked [█████████]Analysed#3063026 | Valid | Information Disclosure | Low | 2025-05-12 | – | 40 |
| Datadog api keys exposed can be used to do all the read and write access to the instanceAnalysed#2307933 | Valid | Information Disclosure | Critical | 2024-01-25 | – | 47 |
| Publicly accessible `█████████` endpoint exposing internal user identifiers and email addressesAnalysed#3360293 | Valid | Information Disclosure | Medium | 2026-02-24 | – | 49 |
| Insecure API Response Leads to Disclosure of Hashed PasswordsAnalysed#2788557 | Valid | Information Disclosure | Medium | 2024-11-26 | – | 61 |
| Unauthenticated Sensitive Information Disclosure on █████████ CVE-2021-38314Analysed#1452774 | Valid | Information Disclosure | Medium | 2025-09-02 | – | 67 |
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.