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 |
|---|---|---|
| 20eventi.wordpress.org | In scope | 2026-11-15 |
| 21.wordpress.org | In scope | 2026-11-15 |
| 211.wordpress.org | In scope | 2026-11-15 |
| 212.wordpress.org | In scope | 2026-11-15 |
| 22.wordpress.org | In scope | 2026-11-15 |
| 222.wordpress.org | In scope | 2026-11-15 |
| 228.wordpress.org | In scope | 2026-11-15 |
| 23.wordpress.org | In scope | 2026-11-15 |
| 230.wordpress.org | In scope | 2026-11-15 |
| 233.wordpress.org | In scope | 2026-11-15 |
| 234.wordpress.org | In scope | 2026-11-15 |
| 235.wordpress.org | In scope | 2026-11-15 |
| 237.wordpress.org | In scope | 2026-11-15 |
| 24.wordpress.org | In scope | 2026-11-15 |
| www.24.wordpress.org | In scope | 2026-11-15 |
| 25.wordpress.org | In scope | 2026-11-15 |
| www.25.wordpress.org | In scope | 2026-11-15 |
| 253aapi.wordpress.org | In scope | 2026-11-15 |
| 253acodex.wordpress.org | In scope | 2026-11-15 |
| 253airclogs.wordpress.org | In scope | 2026-11-15 |
| 253alists.wordpress.org | In scope | 2026-11-15 |
| 253amercantile.wordpress.org | In scope | 2026-11-15 |
| 253aplanet.wordpress.org | In scope | 2026-11-15 |
| 253aprofiles.wordpress.org | In scope | 2026-11-15 |
| 26.wordpress.org | In scope | 2026-11-15 |
| 27.wordpress.org | In scope | 2026-11-15 |
| 28.wordpress.org | In scope | 2026-11-15 |
| 29.wordpress.org | In scope | 2026-11-15 |
| 2fda.wordpress.org | In scope | 2026-11-15 |
| 2fko.wordpress.org | In scope | 2026-11-15 |
| 2ftr.wordpress.org | In scope | 2026-11-15 |
| 2fzh-hk.wordpress.org | In scope | 2026-11-15 |
| www.2qph6v0y0.wordpress.org | In scope | 2026-11-15 |
| 2russ.wordpress.org | In scope | 2026-11-15 |
| 2workingparents.wordpress.org | In scope | 2026-11-15 |
| 3.wordpress.org | In scope | 2026-11-15 |
| www.3.wordpress.org | In scope | 2026-11-15 |
| 30.wordpress.org | In scope | 2026-11-15 |
| 31.wordpress.org | In scope | 2026-11-15 |
| 32.wordpress.org | In scope | 2026-11-15 |
| 33.wordpress.org | In scope | 2026-11-15 |
| 34.wordpress.org | In scope | 2026-11-15 |
| 35.wordpress.org | In scope | 2026-11-15 |
| 36.wordpress.org | In scope | 2026-11-15 |
| 360.wordpress.org | In scope | 2026-11-15 |
| 365.wordpress.org | In scope | 2026-11-15 |
| 37.wordpress.org | In scope | 2026-11-15 |
| 38.wordpress.org | In scope | 2026-11-15 |
| 39.wordpress.org | In scope | 2026-11-15 |
| 3aapi.wordpress.org | In scope | 2026-11-15 |
| 3acodex.wordpress.org | In scope | 2026-11-15 |
| 3airclogs.wordpress.org | In scope | 2026-11-15 |
| 3alists.wordpress.org | In scope | 2026-11-15 |
| 3amercantile.wordpress.org | In scope | 2026-11-15 |
| 3aplanet.wordpress.org | In scope | 2026-11-15 |
| 3aprofiles.wordpress.org | In scope | 2026-11-15 |
| 3c.wordpress.org | In scope | 2026-11-15 |
| 3d.wordpress.org | In scope | 2026-11-15 |
| 3dns-3.wordpress.org | In scope | 2026-11-15 |
| 3g.wordpress.org | In scope | 2026-11-15 |
| 3rahejomhoori.wordpress.org | In scope | 2026-11-15 |
| 3w.wordpress.org | In scope | 2026-11-15 |
| 4.wordpress.org | In scope | 2026-11-15 |
| www.4.wordpress.org | In scope | 2026-11-15 |
| 40.wordpress.org | In scope | 2026-11-15 |
| 404.wordpress.org | In scope | 2026-11-15 |
| 41.wordpress.org | In scope | 2026-11-15 |
| 42.wordpress.org | In scope | 2026-11-15 |
| 43.wordpress.org | In scope | 2026-11-15 |
| 44.wordpress.org | In scope | 2026-11-15 |
| 45.wordpress.org | In scope | 2026-11-15 |
| 46.wordpress.org | In scope | 2026-11-15 |
| 47.wordpress.org | In scope | 2026-11-15 |
| 48.wordpress.org | In scope | 2026-11-15 |
| 48dems.wordpress.org | In scope | 2026-11-15 |
| 49.wordpress.org | In scope | 2026-11-15 |
| 49fengers.wordpress.org | In scope | 2026-11-15 |
| 4ndhe.wordpress.org | In scope | 2026-11-15 |
| 5.wordpress.org | In scope | 2026-11-15 |
| www.5.wordpress.org | In scope | 2026-11-15 |
| 50.wordpress.org | In scope | 2026-11-15 |
| 51.wordpress.org | In scope | 2026-11-15 |
| 52.wordpress.org | In scope | 2026-11-15 |
| 5278.wordpress.org | In scope | 2026-11-15 |
| mail.5278.wordpress.orgmail | In scope | 2026-11-15 |
| 53.wordpress.org | In scope | 2026-11-15 |
| 54.wordpress.org | In scope | 2026-11-15 |
| 55.wordpress.org | In scope | 2026-11-15 |
| 56.wordpress.org | In scope | 2026-11-15 |
| 57.wordpress.org | In scope | 2026-11-15 |
| 58.wordpress.org | In scope | 2026-11-15 |
| 59.wordpress.org | In scope | 2026-11-15 |
| 6.wordpress.org | In scope | 2026-11-15 |
| www.6.wordpress.org | In scope | 2026-11-15 |
| 60.wordpress.org | In scope | 2026-11-15 |
| 61.wordpress.org | In scope | 2026-11-15 |
| 62.wordpress.org | In scope | 2026-11-15 |
| 63.wordpress.org | In scope | 2026-11-15 |
| 64.wordpress.org | In scope | 2026-11-15 |
| 65.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.