Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| [intensedebate.com] SQL Injection Time Based on /changeReplaceOpt.phpAnalysed#1042746 | Valid | SQL Injection | Critical | 2021-01-01 | – | 80 |
| Woocommerce SQL Injection in WC_Report_Coupon_UsageAnalysed#3198980 | Valid | SQL Injection | Medium | 2025-06-24 | – | 96 |
| SQL Injection intensedebate.comAnalysed#1069561 | Valid | SQL Injection | Medium | 2021-01-11 | – | 102 |
| [intensedebate.com] SQL Injection Time Based On /js/commentAction/Analysed#1044698 | Valid | SQL Injection | Critical | 2021-01-01 | – | 130 |
| Sql injection on docs.atavist.comAnalysed#1039315 | Valid | SQL Injection | High | 2020-12-08 | – | 170 |
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 (1,443 analysed so far), which can be wrong. Data as of 2026-11-14.