Program Overview
Discourse runs a bug bounty program on HackerOne. The program has 2 in-scope assets and is managed by HackerOne's triage team.
2
In-Scope Assets
2d
Avg Response
62%
Efficiency
1d
Avg Bounty Time
37d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| https://github.com/discourse/discourse | SOURCE_CODE | Critical | Bounty |
| try.discourse.org | URL | Critical | Bounty |
Tips for Hacking Discourse
- 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 Discourse?
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 Discourse pay bounties?
Yes, Discourse offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does Discourse accept?
Discourse accepts reports for vulnerabilities found in their 2 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.