Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Unauthenticated disclosure of draft/private/pending post titles & IDs via Secure Custom Fields nopriv AJAX field-query handlers (post_object/relationsAnalysed#3893632 | Valid | Access Control | Medium | 2026-09-28 | – | 51 |
| wordpress.org/openverse/: unauthenticated open redirect — `str_replace()`'s 4th arg is a count, not a limit; bypasses WordPress.org SSO allow-listAnalysed#3933198 | Valid | Open Redirect | Medium | 2026-10-30 | – | 31 |
| Unauthenticated Disclosure of Private, Draft, and Password-Protected Post Content via Core Read-Permission Bypass in SCF Reference FieldsAnalysed#4152553 | Valid | Information Disclosure | High | 2026-11-05 | – | 27 |
| Unauthenticated disclosure of private and hidden forum content in bbPress via the WordPress core REST single-item endpointAnalysed#3801107 | Valid | Access Control | Critical | 2026-10-12 | – | 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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.