Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Information / sensitive data disclosure on some endpoints#273726 | Valid | Information Disclosure | – | 2018-08-22 | – | 32 |
| Unauthenticated Disclosure of Private, Draft, and Password-Protected Post Content via Core Read-Permission Bypass in SCF Reference Fields#4152553 | Valid | Information Disclosure | High | 2026-11-05 | – | 27 |
| Information Disclosure - Unauthen Leak Private Content#4053546 | Valid | Information Disclosure | Medium | 2026-10-10 | – | 27 |
| PII of users can be downloaded from export pages#1172852 | Valid | Information Disclosure | Medium | 2023-05-12 | – | 17 |
| Administrator(s) Information disclosure via JSON on wordpress.org#221734 | N/A | Information Disclosure | – | 2017-04-19 | – | 4 |
| 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 (1,199 analysed so far), which can be wrong. Data as of 2026-11-14.