Program Overview
Concrete CMS runs a vulnerability disclosure program on HackerOne. The program has 1 in-scope assets.
1
In-Scope Assets
3d
Avg Response
79%
Efficiency
36d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| https://github.com/concrete5/concrete5 | SOURCE_CODE | Critical | No Bounty |
Out-of-Scope Assets
- *.concrete5.org
- *.concretecms.com
- *.concretecms.org
Tips for Hacking Concrete CMS
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking Concrete CMS?
Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does Concrete CMS pay bounties?
No, Concrete CMS runs a Vulnerability Disclosure Program (VDP) without monetary rewards. You may receive recognition or swag.
What types of vulnerabilities does Concrete CMS accept?
Concrete CMS accepts reports for vulnerabilities found in their 1 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.