Skip to content

Bug bounty reports15,219

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

Program:WordPress
Status
Severity
Weakness:No weakness recorded
Clear
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Open API For Username enumeration#385322N/ANo weakness recordedLow2018-07-23–25
Reflected Swf XSS In ( plugins.svn.wordpress.org )#270060ValidNo weakness recordedMedium2018-09-27–21
Buddypress 2.9.1 - Exceeding the maximum upload size - XSS leading to potential RCE.#263109ValidNo weakness recordedMedium2017-11-02–14
code.wordpress.net subdomain Takeover#295330ValidNo weakness recordedMedium2018-03-11–9
[Buddypress] Arbitrary File Deletion through bp_avatar_set#183568ValidNo weakness recordedHigh2017-08-22–9
Lack of Password Confirmation when Changing Password and Email#224214DuplicateNo weakness recorded–2017-04-28–7
Privilege Escalation in BuddyPress core allows Moderate to Administrator#837018ValidNo weakness recordedMedium2020-05-22–6
Wordpress 4.8.1 - Rogue editor leads to RCE. And the risks of same origin frame scripting in general#263718InformativeNo weakness recordedHigh2017-10-04–4

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 (2,699 analysed so far), which can be wrong. Data as of 2026-11-15.