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
Year:2016
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Local File Inclusion path bypassAnalysed#147570ValidMisconfiguration and Insecure Design–2016-08-19–13
CSRF Full Account Takeover#152052ValidCross-Site Request Forgery–2016-08-12–11
Local File Inclusion Vulnerability in Concrete5 version 5.7.3.1#59665ValidMisconfiguration and Insecure Design–2016-06-26–11
Multiple Stored Cross Site Scripting Vulnerabilities in Concrete5 version 5.7.3.1#59662ValidCross-site Scripting–2016-06-26–3
Multiple Cross Site Request Forgery Vulnerabilities in Concrete5 version 5.7.3.1#59660ValidCross-Site Request Forgery–2016-06-26–3
stored XSS in concrete5 5.7.2.1#38890ValidCross-site Scripting–2016-04-26–3
SQL injection in conc/index.php/ccm/system/search/users/submit#38778ValidSQL Injection–2016-04-26–3
Stored XSS in adding fileset#42248ValidCross-site Scripting–2016-04-26–2
ProBlog 2.6.6 CSRF Exploit#133847ValidCross-Site Request Forgery–2016-05-22–1

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.