Bug bounty program
WO
WordPress
Most upvoted reports96
All reports| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Stored XSS VulnerabilityAnalysed#643908 | Cross-site Scripting | 2019-07-18 | – | 403 |
| Stored XSS in Private Message component (BuddyPress)Analysed#487081 | Cross-site Scripting | 2019-03-08 | – | 337 |
| RCE as Admin defeats WordPress hardening and file permissionsAnalysed#436928 | File and Path Handling | 2020-06-09 | – | 164 |
| Stored XSS on byddypress Plug-in via groups nameAnalysed#592316 | Cross-site Scripting | 2019-07-27 | – | 132 |
| Wordpress unzip_file path traversalAnalysed#205481 | Misconfiguration and Insecure Design | 2020-01-29 | – | 119 |
| Reflected XSS on https://make.wordpress.org via 'channel' parameterAnalysed#659419 | Cross-site Scripting | 2019-08-26 | – | 97 |
| CSRF to HTML Injection in CommentsAnalysed#428019 | Cross-Site Request Forgery | 2019-05-13 | – | 95 |
| Privilege Escalation via REST API to Administrator leads to RCEAnalysed#1107282 | Access Control | 2021-05-17 | – | 92 |
| Clickjacking on donation pageAnalysed#921709 | Misconfiguration and Insecure Design | 2020-07-16 | – | 90 |
| Potential unprivileged Stored XSS through wp_targeted_link_relAnalysed#509930 | Cross-site Scripting | 2020-01-08 | – | 80 |
Subdomains29,502
| Name | Scope | First seen |
|---|---|---|
| access.wordpress.orgvpn | In scope | 2026-11-15 |
| www.access.wordpress.orgvpn | In scope | 2026-11-15 |
| access1.wordpress.orgvpn | In scope | 2026-11-15 |
| access2.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix1.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix2.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix.de.wordpress.orgvpn | In scope | 2026-11-15 |
| remote.de.wordpress.orgvpn | In scope | 2026-11-15 |
| sslvpn.de.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn.de.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn.es.wordpress.orgvpn | In scope | 2026-11-15 |
| horizon.wordpress.orgvpn | In scope | 2026-11-15 |
| ic-asa5520-vpn-fw.wordpress.orgvpn | In scope | 2026-11-15 |
| kesc-vpn.wordpress.orgvpn | In scope | 2026-11-15 |
| openvpn.wordpress.orgvpn | In scope | 2026-11-15 |
| pw.openvpn.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix.planet.wordpress.orgvpn | In scope | 2026-11-15 |
| remote.planet.wordpress.orgvpn | In scope | 2026-11-15 |
| sslvpn.planet.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn.planet.wordpress.orgvpn | In scope | 2026-11-15 |
| citrix.profiles.wordpress.orgvpn | In scope | 2026-11-15 |
| remote.profiles.wordpress.orgvpn | In scope | 2026-11-15 |
| sslvpn.profiles.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn.profiles.wordpress.orgvpn | In scope | 2026-11-15 |
| rdp.wordpress.orgvpn | In scope | 2026-11-15 |
| rdweb.wordpress.orgvpn | In scope | 2026-11-15 |
| remote.wordpress.orgvpn | In scope | 2026-11-15 |
| www.remote.wordpress.orgvpn | In scope | 2026-11-15 |
| remote1.wordpress.orgvpn | In scope | 2026-11-15 |
| remote2.wordpress.orgvpn | In scope | 2026-11-15 |
| ssl-vpn.wordpress.orgvpn | In scope | 2026-11-15 |
| ul-asa5520-vpn-fw.wordpress.orgvpn | In scope | 2026-11-15 |
| vdi.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn-test.wordpress.orgtest, vpn | In scope | 2026-11-15 |
| vpn-uk.wordpress.orgvpn | In scope | 2026-11-15 |
| www.vpn.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn02.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn1.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn2.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn3.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn4.wordpress.orgvpn | In scope | 2026-11-15 |
| vpn5.wordpress.orgvpn | In scope | 2026-11-15 |
29,002 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.