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 |
|---|---|---|
| 0.wordpress.org | In scope | 2026-11-15 |
| 000.wordpress.org | In scope | 2026-11-15 |
| 007.wordpress.org | In scope | 2026-11-15 |
| 01.wordpress.org | In scope | 2026-11-15 |
| 02.wordpress.org | In scope | 2026-11-15 |
| 03.wordpress.org | In scope | 2026-11-15 |
| 080.wordpress.org | In scope | 2026-11-15 |
| mail.080.wordpress.orgmail | In scope | 2026-11-15 |
| 0nanii0.wordpress.org | In scope | 2026-11-15 |
| 1.wordpress.org | In scope | 2026-11-15 |
| www.1.wordpress.org | In scope | 2026-11-15 |
| 10.wordpress.org | In scope | 2026-11-15 |
| 100.wordpress.org | In scope | 2026-11-15 |
| 1000.wordpress.org | In scope | 2026-11-15 |
| 100mudcats.wordpress.org | In scope | 2026-11-15 |
| 101.wordpress.org | In scope | 2026-11-15 |
| 101usesforafork.wordpress.org | In scope | 2026-11-15 |
| 103.wordpress.org | In scope | 2026-11-15 |
| 105.wordpress.org | In scope | 2026-11-15 |
| 106.wordpress.org | In scope | 2026-11-15 |
| 109.wordpress.org | In scope | 2026-11-15 |
| 11.wordpress.org | In scope | 2026-11-15 |
| www.11.wordpress.org | In scope | 2026-11-15 |
| 110.wordpress.org | In scope | 2026-11-15 |
| 11091521400593.wordpress.org | In scope | 2026-11-15 |
| 111.wordpress.org | In scope | 2026-11-15 |
| 1111.wordpress.org | In scope | 2026-11-15 |
| 11192521403954.wordpress.org | In scope | 2026-11-15 |
| 11192521404255.wordpress.org | In scope | 2026-11-15 |
| 112.wordpress.org | In scope | 2026-11-15 |
| 11285521401250.wordpress.org | In scope | 2026-11-15 |
| 11290521402560.wordpress.org | In scope | 2026-11-15 |
| 114.wordpress.org | In scope | 2026-11-15 |
| 116profile.wordpress.org | In scope | 2026-11-15 |
| 117.wordpress.org | In scope | 2026-11-15 |
| 118.wordpress.org | In scope | 2026-11-15 |
| 119.wordpress.org | In scope | 2026-11-15 |
| 11mar11.wordpress.org | In scope | 2026-11-15 |
| 12.wordpress.org | In scope | 2026-11-15 |
| www.12.wordpress.org | In scope | 2026-11-15 |
| 120.wordpress.org | In scope | 2026-11-15 |
| 121.wordpress.org | In scope | 2026-11-15 |
| 123.wordpress.org | In scope | 2026-11-15 |
| www.123.wordpress.org | In scope | 2026-11-15 |
| 1234.wordpress.org | In scope | 2026-11-15 |
| 12345.wordpress.org | In scope | 2026-11-15 |
| 123456.wordpress.org | In scope | 2026-11-15 |
| 125.wordpress.org | In scope | 2026-11-15 |
| 126.wordpress.org | In scope | 2026-11-15 |
| 128.wordpress.org | In scope | 2026-11-15 |
| 129.wordpress.org | In scope | 2026-11-15 |
| 12o.wordpress.org | In scope | 2026-11-15 |
| 13.wordpress.org | In scope | 2026-11-15 |
| www.13.wordpress.org | In scope | 2026-11-15 |
| 130.wordpress.org | In scope | 2026-11-15 |
| 131.wordpress.org | In scope | 2026-11-15 |
| 132.wordpress.org | In scope | 2026-11-15 |
| 134.wordpress.org | In scope | 2026-11-15 |
| 137.wordpress.org | In scope | 2026-11-15 |
| 14.wordpress.org | In scope | 2026-11-15 |
| www.14.wordpress.org | In scope | 2026-11-15 |
| 15.wordpress.org | In scope | 2026-11-15 |
| www.15.wordpress.org | In scope | 2026-11-15 |
| 16.wordpress.org | In scope | 2026-11-15 |
| www.16.wordpress.org | In scope | 2026-11-15 |
| 162.wordpress.org | In scope | 2026-11-15 |
| 163.wordpress.org | In scope | 2026-11-15 |
| 169.wordpress.org | In scope | 2026-11-15 |
| 17.wordpress.org | In scope | 2026-11-15 |
| www.17.wordpress.org | In scope | 2026-11-15 |
| 170.wordpress.org | In scope | 2026-11-15 |
| 18.wordpress.org | In scope | 2026-11-15 |
| www.18.wordpress.org | In scope | 2026-11-15 |
| 187.wordpress.org | In scope | 2026-11-15 |
| 19.wordpress.org | In scope | 2026-11-15 |
| www.19.wordpress.org | In scope | 2026-11-15 |
| 192.wordpress.org | In scope | 2026-11-15 |
| 1c.wordpress.org | In scope | 2026-11-15 |
| 1kib.wordpress.org | In scope | 2026-11-15 |
| 1swbeavers.wordpress.org | In scope | 2026-11-15 |
| 1trmst2hn.wordpress.org | In scope | 2026-11-15 |
| 2.wordpress.org | In scope | 2026-11-15 |
| www.2.wordpress.org | In scope | 2026-11-15 |
| 20.wordpress.org | In scope | 2026-11-15 |
| www.20.wordpress.org | In scope | 2026-11-15 |
| 2006.wordpress.org | In scope | 2026-11-15 |
| 2008.wordpress.org | In scope | 2026-11-15 |
| 2009.wordpress.org | In scope | 2026-11-15 |
| 2010.wordpress.org | In scope | 2026-11-15 |
| www.2010.wordpress.org | In scope | 2026-11-15 |
| 2011.wordpress.org | In scope | 2026-11-15 |
| www.2011.wordpress.org | In scope | 2026-11-15 |
| 2012.wordpress.org | In scope | 2026-11-15 |
| www.2012.wordpress.org | In scope | 2026-11-15 |
| 2013.wordpress.org | In scope | 2026-11-15 |
| www.2013.wordpress.org | In scope | 2026-11-15 |
| 203.wordpress.org | In scope | 2026-11-15 |
| 204.wordpress.org | In scope | 2026-11-15 |
| 205.wordpress.org | In scope | 2026-11-15 |
| 209.wordpress.org | 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.