Skip to content

Bug bounty reports15,219

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

Program:WordPress
Status
Severity:High
Clear
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:A user account
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Stored XSS VulnerabilityAnalysed#643908ValidCross-site ScriptingHigh2019-07-18–403
Privilege Escalation via REST API to Administrator leads to RCEAnalysed#1107282ValidAccess ControlHigh2021-05-17–92
Potential unprivileged Stored XSS through wp_targeted_link_relAnalysed#509930ValidCross-site ScriptingHigh2020-01-08–80
Logic flaw in the Post creation process allows creating posts with arbitrary types without needing the corresponding nonceAnalysed#404323ValidInput Validation and LogicHigh2019-02-14–38
WordPress 7.1 Media Processing Race Enables Persistent PHP File Write and Author-to-RCEAnalysed#3923967ValidCommand and Code InjectionHigh2026-10-21–37
Add users to groups who have restricted group invitesAnalysed#538008ValidAccess ControlHigh2019-07-27–32
wordpress.org Rosetta: invite stores unvalidated role — Editor can assign site Administrator despite editable_rolesAnalysed#3942522ValidAccess ControlHigh2026-11-05–24
Wordpress 4.7 - CSRF -> HTTP SSRF any private ip:port and basic-authAnalysed#187520ValidCross-Site Request ForgeryHigh2017-11-20–21

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, where there is one, which can be wrong. Data as of 2026-11-15.