- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
While we do not operate a formal bug bounty or provide monetary rewards, we actively support responsible disclosure and welcome reports from the security research community.
- Hall of fame
-
No
EAB no longer maintains a Wall of Fame.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 1 excluded.
Domains 2
- theforage.com
- www.theforage.com
Out of scope (1)
- All other endpoints are out-of-scope.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Forage's policy. "We" in these lines means the program, not this site.
While testing
-
Do not use automated scanning tools.
-
Include as much information as possible including a description of the bug, its impact, severity, and steps for reproducing the vulnerability.
-
If possible, please include a remediation strategy.
-
We must be able to reproduce the vulnerability through a proof of concept (PoC) or technical steps of reproduction.
Not accepted
-
Vulnerabilities on third party tools that we use (unless they lead to a vulnerability on our main system - lateral movement)
-
Vulnerabilities that rely on physical attacks, social engineering, spamming, denial of service (DoS) attacks, etc.
-
Vulnerabilities affecting outdated hardware and software
-
Vulnerabilities discovered from automated tools
-
Vulnerabilities in third-party APIs
-
Vulnerabilities that have already been reported
-
Vulnerabilities that do not have a working proof-of-concept / practical demonstration
-
Vulnerabilities already known to us
-
Vulnerabilities that we can't reproduce
-
Vulnerabilities that we cannot realistically fix
-
Misconfigured SPF / DMARC / DKIM / DNSSec settings
-
Misconfigured SSL/TLS settings
-
Lack of reCAPTCHA / rate limits
-
Lack of auto sign-out after a period of inactivity
-
Lack of re-authentication for account actions
-
Lack of Cookie flags
-
Lack of email verification/notification
-
MFA Bypass that use Google OAuth
-
Password reset token leakage
-
Known-vulnerable libraries which lead to low-impact vulnerability (e.g. outdated jQuery)
-
CORS misconfigurations which leak the /info websocket endpoint (other websocket findings are accepted)
-
Google Maps API key disclosure
-
Best practice issues that are not directly related to security posture, such as password strength, validation of data types and length
-
Self-exploitation (self-XSS, password reset links or cookie reuse)
-
Session management on concurrent sign in / signup / email change / password change / etc.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.