Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Blind SQL Injection on █████ via URI Path#2266081 | Valid | SQL Injection | – | 2024-02-14 | – | 29 |
| SQLi at █████ parameter#3277276 | Valid | SQL Injection | Critical | 2026-02-24 | – | 42 |
| Sqli on ██████ search functionality#2453475 | Valid | SQL Injection | Medium | 2024-06-25 | – | 47 |
| SQLi At `███████` via `theme_name`#3293803 | Valid | SQL Injection | Critical | 2026-02-24 | – | 62 |
| sqli on █████████ search functionality#2446550 | Valid | SQL Injection | Medium | 2024-06-25 | – | 72 |
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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.