Skip to content

Bug bounty reports15,219

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

Program:WordPress
Status
Severity
Weakness:Cross-Site Request Forgery
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 filters6 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
CSRF in Profile Fields allows deleting any field in BuddyPress#836187ValidCross-Site Request Forgery–2020-05-22–5
CSRF on comment post#914232N/ACross-Site Request Forgery–2020-07-16–5
CSRF to add admin [wordpress]#149589ValidCross-Site Request Forgery–2017-06-30–15
Wordpress 4.7 - CSRF -> HTTP SSRF any private ip:port and basic-auth#187520ValidCross-Site Request Forgery–2017-11-20–21
Arbitrary change of blog's background image via CSRF#881855ValidCross-Site Request Forgery–2020-12-14–21
CSRF to HTML Injection in Comments#428019ValidCross-Site Request Forgery–2019-05-13–95

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

Updated AboutDevelopersSign in