Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Authenticated Code Execution through Phar deserialization in CSV Importer as Shop manager in WooCommerceAnalysed#403083 | Valid | Deserialization and Object Injection | High | 2019-12-19 | – | 84 |
| WordPress SOME bug in plupload.flash.swf leading to RCEAnalysed#134738 | Valid | Command and Code Injection | – | 2016-07-10 | – | 50 |
| Unauthenticated RCE in VaultpressAnalysed#236552 | Valid | No weakness recorded | Critical | 2017-09-15 | – | 31 |
| RCE via Print function [Simplenote 1.1.3 - Desktop app]Analysed#358049 | Valid | Command and Code Injection | High | 2018-07-26 | – | 28 |
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.