Skip to content

Bug bounty reports15,219

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

Program:Concrete CMS
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 filters4 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
No csrf protection on index.php/ccm/system/user/add_group, index.php/ccm/system/user/remove_group#64184ValidCross-Site Request Forgery–2015-08-26–1
ProBlog 2.6.6 CSRF Exploit#133847ValidCross-Site Request Forgery–2016-05-22–1
Multiple Cross Site Request Forgery Vulnerabilities in Concrete5 version 5.7.3.1#59660ValidCross-Site Request Forgery–2016-06-26–3
CSRF Full Account Takeover#152052ValidCross-Site Request Forgery–2016-08-12–11

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