Whereby
Bug bounty on security.txt whereby.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
Any form of compensation will be considered but will not be guaranteed.
- Safe harbor
-
Full
Whereby will not take legal action against security researchers who submit vulnerability reports following the terms indicated in this document or for accidental, good faith violations of this policy, as long as the reason for the accidental / good faith violation has been clearly stated.
- Hall of fame
-
Yes
Vulnerabilities reported and acknowledged to be valid are subject to public recognition of the author on our Hall of Fame page , depending on the criticality of the vulnerability.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- whereby.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Whereby's policy.
While testing
-
Disrupt Whereby systems or services.
-
Modify or destroy data of Whereby systems or services.
-
Disclose any found vulnerabilities to the public or third parties.
-
Violate the privacy of Whereby users, employees, systems or services.
-
Use high-intensity invasive, automatic or destructive scanning / exploit tools.
-
Require financial compensation under threat of withholding or release of vulnerabilities to the public.
-
Use malware.
-
Use the discovered vulnerability in any way beyond proving / demonstrating its existence (e.g., exploit the vulnerability to pivot to internal systems, compromise a system and persistently maintaining access to it, etc).
-
Use social engineering, spam or phishing techniques.
-
Submit documents in any format other than .pdf or video files.
Not accepted
-
TLS/SSL configuration weaknesses (e.g., weak / insecure cipher suites, renegotiation attacks).
-
Vulnerabilities obtained via the compromise of a Whereby customer or Whereby employee accounts.
-
Denial of Service (DoS / DDoS) attacks against Whereby systems or services.
-
User interface bugs or typos.
-
Login / logout CSRF.
-
Missing HTTP security headers that do not lead directly to a vulnerability.
-
Presence / absence of DNS records.
-
Password, email and account policies (e.g: email id verification, password complexity).
-
Lack of CSRF tokens in non-sensitive actions.
-
Attacks requiring physical access to a user's device.
-
Report the use of a known-vulnerable library (without evidence of exploitability).
-
Missing cookie flags without clearly identified security impact.
-
Open redirectors.
-
CSRF or clickjacking with no practical use to attackers.
-
CSRF that requires the knowledge of a secret.
-
Exposed metrics or other type of not confidential data.
-
Missing best practices, configuration or policy suggestions.
-
Vulnerabilities that require a man-in-the-middle scenario to be exploited.
-
Previously reported vulnerabilities or security vulnerabilities already discovered by internal procedures are not eligible for a reward.
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 12 Nov 2026. Last checked 3 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.