Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Disclosed bug bounty reports
Report	Status	Weakness	Severity	Disclosed	Bounty	Votes
Unauthenticated disclosure of draft/private/pending post titles & IDs via Secure Custom Fields nopriv AJAX field-query handlers (post_object/relations#3893632	Valid	Access Control	Medium	2026-09-28	–	51
wordpress.org/openverse/: unauthenticated open redirect — `str_replace()`'s 4th arg is a count, not a limit; bypasses WordPress.org SSO allow-list#3933198	Valid	Open Redirect	Medium	2026-10-30	–	31
Unauthenticated Disclosure of Private, Draft, and Password-Protected Post Content via Core Read-Permission Bypass in SCF Reference Fields#4152553	Valid	Information Disclosure	High	2026-11-05	–	27
Unauthenticated disclosure of private and hidden forum content in bbPress via the WordPress core REST single-item endpoint#3801107	Valid	Access Control	Critical	2026-10-12	–	23
Unauthenticated private CSV export of Meetup organizer PII via broken authz check in WordCamp Reports#3871816	Valid	Access Control	High	2026-11-05	–	16
pre-auth Stored XSS in comments via javascript: url when administrator edits user supplied comment#633231	Valid	Cross-site Scripting	–	2020-08-18	–	12
Unauthenticated hidden groups disclosure via Ajax groups search#282176	Valid	Access Control	–	2017-11-02	–	6

Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (965 analysed so far), which can be wrong. Data as of 2026-11-14.