Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Reflected XSS on https://make.wordpress.org via 'channel' parameterAnalysed#659419 | Valid | Cross-site Scripting | High | 2019-08-26 | – | 97 |
| 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 |
| Wordpress 4.7.2 - Two XSS in Media Upload when file too large.Analysed#203515 | Valid | Cross-site Scripting | High | 2017-07-17 | – | 23 |
| Instamojo CampTix: fail-open MAC + webhook Credit without binding payment to orderAnalysed#3941626 | Valid | Access Control | High | 2026-11-05 | – | 17 |
| Unauthenticated private CSV export of Meetup organizer PII via broken authz check in WordCamp ReportsAnalysed#3871816 | Valid | Access Control | High | 2026-11-05 | – | 16 |
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.