Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Wordpress 4.8.1 - Rogue editor leads to RCE. And the risks of same origin frame scripting in general#263718 | Informative | No weakness recorded | – | 2017-10-04 | – | 4 |
| antispambot does not always escape <, >, &, " and '#298218 | Informative | Cross-site Scripting | – | 2019-09-16 | – | 3 |
| Stored XSS in WordPress#276105 | Informative | Cross-site Scripting | – | 2018-02-02 | – | 3 |
| Clickjacking irclogs.wordpress.org#267075 | Informative | Misconfiguration and Insecure Design | – | 2017-10-12 | – | 2 |
| UnResolved ChangeSet are Visible to Public That also Causes Information Disclosure#282843 | Informative | Information Disclosure | – | 2018-02-05 | – | 1 |
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 (779 analysed so far), which can be wrong. Data as of 2026-11-14.