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 |
|---|---|---|
| adfs.wordpress.orgauth | In scope | 2026-11-15 |
| auth.wordpress.orgauth | In scope | 2026-11-15 |
| auth-hack.wordpress.orgauth | In scope | 2026-11-15 |
| radius.auth.wordpress.orgauth | In scope | 2026-11-15 |
| auth1.wordpress.orgauth | In scope | 2026-11-15 |
| auth2.wordpress.orgauth | In scope | 2026-11-15 |
| auth3.wordpress.orgauth | In scope | 2026-11-15 |
| cas.wordpress.orgauth | In scope | 2026-11-15 |
| cas1.wordpress.orgauth | In scope | 2026-11-15 |
| cas2.wordpress.orgauth | In scope | 2026-11-15 |
| cas3.wordpress.orgauth | In scope | 2026-11-15 |
| iam.wordpress.orgauth | In scope | 2026-11-15 |
| www.iam1212505042.wordpress.orgauth | In scope | 2026-11-15 |
| identity.wordpress.orgauth | In scope | 2026-11-15 |
| idp.wordpress.orgauth | In scope | 2026-11-15 |
| idp-test.wordpress.orgauth, test | In scope | 2026-11-15 |
| idp2.wordpress.orgauth | In scope | 2026-11-15 |
| login.wordpress.orgauth | In scope | 2026-11-15 |
| autoconfig.login.wordpress.orgauth | In scope | 2026-11-15 |
| autodiscover.login.wordpress.orgauth, mail | In scope | 2026-11-15 |
| webdisk.login.wordpress.orgauth | In scope | 2026-11-15 |
| www.login.wordpress.orgauth | In scope | 2026-11-15 |
| login1.wordpress.orgauth | In scope | 2026-11-15 |
| login2.wordpress.orgauth | In scope | 2026-11-15 |
| oauth.wordpress.orgauth | In scope | 2026-11-15 |
| okta.wordpress.orgauth | In scope | 2026-11-15 |
| auth.planet.wordpress.orgauth | In scope | 2026-11-15 |
| iam.planet.wordpress.orgauth | In scope | 2026-11-15 |
| login.planet.wordpress.orgauth | In scope | 2026-11-15 |
| okta.planet.wordpress.orgauth | In scope | 2026-11-15 |
| signin.planet.wordpress.orgauth | In scope | 2026-11-15 |
| sso.planet.wordpress.orgauth | In scope | 2026-11-15 |
| auth.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| iam.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| login.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| okta.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| signin.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| sso.profiles.wordpress.orgauth | In scope | 2026-11-15 |
| signin.wordpress.orgauth | In scope | 2026-11-15 |
| sso.wordpress.orgauth | In scope | 2026-11-15 |
| www.sso.wordpress.orgauth | In scope | 2026-11-15 |
| ws-lon-oauth1.wordpress.orgauth | 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.