Skip to content
Connect AISign inSign up free

Bug bounty program

WO

WordPress

Open on HackerOneAtlas
Platform
HackerOne
Bounties
Pays
Assets in scope
23
Disclosed reports
96
Subdomains
29,502
Vendor on CyberSIXT
WordPress (405 CVEs, 7 exploited)

Most upvoted reports96

All reports
Most upvoted reports of WordPress
ReportWeaknessDisclosedBountyVotes
Stored XSS VulnerabilityAnalysed#643908Cross-site Scripting2019-07-18–403
Stored XSS in Private Message component (BuddyPress)Analysed#487081Cross-site Scripting2019-03-08–337
RCE as Admin defeats WordPress hardening and file permissionsAnalysed#436928File and Path Handling2020-06-09–164
Stored XSS on byddypress Plug-in via groups nameAnalysed#592316Cross-site Scripting2019-07-27–132
Wordpress unzip_file path traversalAnalysed#205481Misconfiguration and Insecure Design2020-01-29–119
Reflected XSS on https://make.wordpress.org via 'channel' parameterAnalysed#659419Cross-site Scripting2019-08-26–97
CSRF to HTML Injection in CommentsAnalysed#428019Cross-Site Request Forgery2019-05-13–95
Privilege Escalation via REST API to Administrator leads to RCEAnalysed#1107282Access Control2021-05-17–92
Clickjacking on donation pageAnalysed#921709Misconfiguration and Insecure Design2020-07-16–90
Potential unprivileged Stored XSS through wp_targeted_link_relAnalysed#509930Cross-site Scripting2020-01-08–80

Subdomains29,502

Root
Scope
Name suggests:API
First seen
Text fileClear filters169 names
Subdomains of WordPress
NameScopeFirst seen
db2.api.ord.wordpress.orgapiIn scope2026-11-15
db3.api.ord.wordpress.orgapiIn scope2026-11-15
db4.api.ord.wordpress.orgapiIn scope2026-11-15
u003edb1.api.ord.wordpress.orgapiIn scope2026-11-15
u003edb2.api.ord.wordpress.orgapiIn scope2026-11-15
u003edb3.api.ord.wordpress.orgapiIn scope2026-11-15
u003edb4.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb1.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb10.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb11.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb12.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb13.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb14.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb2.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb3.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb4.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb5.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb6.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb7.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb8.api.ord.wordpress.orgapiIn scope2026-11-15
u003eweb9.api.ord.wordpress.orgapiIn scope2026-11-15
web1.api.ord.wordpress.orgapiIn scope2026-11-15
web10.api.ord.wordpress.orgapiIn scope2026-11-15
web11.api.ord.wordpress.orgapiIn scope2026-11-15
web12.api.ord.wordpress.orgapiIn scope2026-11-15
web13.api.ord.wordpress.orgapiIn scope2026-11-15
web14.api.ord.wordpress.orgapiIn scope2026-11-15
web2.api.ord.wordpress.orgapiIn scope2026-11-15
web3.api.ord.wordpress.orgapiIn scope2026-11-15
web4.api.ord.wordpress.orgapiIn scope2026-11-15
web5.api.ord.wordpress.orgapiIn scope2026-11-15
web6.api.ord.wordpress.orgapiIn scope2026-11-15
web7.api.ord.wordpress.orgapiIn scope2026-11-15
web8.api.ord.wordpress.orgapiIn scope2026-11-15
web9.api.ord.wordpress.orgapiIn scope2026-11-15
origin-api.wordpress.orgapiIn scope2026-11-15
api.planet.wordpress.orgapiIn scope2026-11-15
cdq-api.planet.wordpress.orgapiIn scope2026-11-15
cim-api.planet.wordpress.orgapiIn scope2026-11-15
cim-api-dev.planet.wordpress.orgapi, devIn scope2026-11-15
cim-api-qa.planet.wordpress.orgapi, testIn scope2026-11-15
cim-api-uat.planet.wordpress.orgapi, testIn scope2026-11-15
gws-api-sandbox.planet.wordpress.orgapi, testIn scope2026-11-15
ks-inventory-api.planet.wordpress.orgapiIn scope2026-11-15
ks-invoice-api.planet.wordpress.orgapiIn scope2026-11-15
ks-limits-api.planet.wordpress.orgapiIn scope2026-11-15
ks-order-api.planet.wordpress.orgapiIn scope2026-11-15
ks-program-api.planet.wordpress.orgapiIn scope2026-11-15
vendor-api.planet.wordpress.orgapiIn scope2026-11-15
api.profiles.wordpress.orgapiIn scope2026-11-15
cdq-api.profiles.wordpress.orgapiIn scope2026-11-15
cim-api.profiles.wordpress.orgapiIn scope2026-11-15
cim-api-dev.profiles.wordpress.orgapi, devIn scope2026-11-15
cim-api-qa.profiles.wordpress.orgapi, testIn scope2026-11-15
cim-api-uat.profiles.wordpress.orgapi, testIn scope2026-11-15
gws-api-sandbox.profiles.wordpress.orgapi, testIn scope2026-11-15
ks-inventory-api.profiles.wordpress.orgapiIn scope2026-11-15
ks-invoice-api.profiles.wordpress.orgapiIn scope2026-11-15
ks-limits-api.profiles.wordpress.orgapiIn scope2026-11-15
ks-order-api.profiles.wordpress.orgapiIn scope2026-11-15
ks-program-api.profiles.wordpress.orgapiIn scope2026-11-15
vendor-api.profiles.wordpress.orgapiIn scope2026-11-15
rpc.wordpress.orgapiIn scope2026-11-15
soap.wordpress.orgapiIn scope2026-11-15
api.staging.wordpress.orgapi, stagingIn scope2026-11-15
api.test.wordpress.orgapi, testIn scope2026-11-15
vendor-api.wordpress.orgapiIn scope2026-11-15
webservice.wordpress.orgapiIn scope2026-11-15
webservices.wordpress.orgapiIn scope2026-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.

CyberSIXTSignal over noise
Sign inSign up free

Updated