Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| WordPress Automatic Update Protocol Does Not Authenticate Updates Provided by the Server#228854 | N/A | Cryptography | – | 2019-07-22 | – | 2 |
| Administrator(s) Information disclosure via JSON on wordpress.org#221734 | N/A | Information Disclosure | – | 2017-04-19 | – | 4 |
| CSRF on comment post#914232 | N/A | Cross-Site Request Forgery | – | 2020-07-16 | – | 5 |
| Account takeover vulnerability by editor role privileged users/attackers via clickjacking#388254 | N/A | Misconfiguration and Insecure Design | – | 2018-09-03 | – | 8 |
| Stored XSS on Wordpress 5.3 via Title Post#754352 | N/A | Cross-site Scripting | – | 2019-12-10 | – | 9 |
| Open API For Username enumeration#385322 | N/A | No weakness recorded | – | 2018-07-23 | – | 25 |
| Unauthenticated WordPress Database Repair DoS#2786591 | N/A | Denial of Service | High | 2024-10-18 | – | 70 |
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.