Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| RCE as Admin defeats WordPress hardening and file permissionsAnalysed#436928 | Valid | File and Path Handling | Critical | 2020-06-09 | – | 164 |
| Privilege Escalation via REST API to Administrator leads to RCEAnalysed#1107282 | Valid | Access Control | High | 2021-05-17 | – | 92 |
| Pivilege escalation of any new user to Keymaster caused by CSRFAnalysed#2999394 | Valid | Access Control | Medium | 2025-09-13 | – | 61 |
| Logic flaw in the Post creation process allows creating posts with arbitrary types without needing the corresponding nonceAnalysed#404323 | Valid | Input Validation and Logic | High | 2019-02-14 | – | 38 |
| wordpress.org Rosetta: invite stores unvalidated role — Editor can assign site Administrator despite editable_rolesAnalysed#3942522 | Valid | Access Control | High | 2026-11-05 | – | 24 |
| XSS via unicode characters in upload filenameAnalysed#179695 | Valid | Cross-site Scripting | Medium | 2020-08-28 | – | 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, where there is one, which can be wrong. Data as of 2026-11-15.