Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Wordpress unzip_file path traversalAnalysed#205481 | Valid | Misconfiguration and Insecure Design | Medium | 2020-01-29 | – | 119 |
| Potential unprivileged Stored XSS through wp_targeted_link_relAnalysed#509930 | Valid | Cross-site Scripting | High | 2020-01-08 | – | 80 |
| Authenticated Stored Cross-site Scripting in bbPressAnalysed#881918 | Valid | Cross-site Scripting | Medium | 2020-06-29 | – | 24 |
| Stored XSS on Broken Themes via filenameAnalysed#406289 | Valid | Cross-site Scripting | Low | 2020-08-25 | – | 23 |
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 (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.