Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Bookwhen

Vulnerability disclosure program on security.txt bookwhen.com

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
4
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]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No However, at this time, we do not offer a paid bug bounty programme.
Response
Within 5 days After you have submitted your report, we will usually respond to your report within 5 working days
Safe harbor
Full We will work with you to understand and resolve the issue quickly, and we will not bring or support a legal claim against you in connection with your report.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

4 assets you may test, 1 excluded.

APIs 1

  • api.bookwhen.com

Domains 1

  • bookwhen.com

Wildcard domains 1

  • bookwhen.com subdomains

Products and areas 1

  • Our booking pages where they are embedded in a customer’s own website.
Out of scope (1)
  • Third party services that we use but do not operate, for example our payment providers, email delivery and help centre

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Bookwhen's policy. "We" in these lines means the program, not this site.

While testing

  • You must not break any applicable law or regulations.
  • Do not access or modify, or attempt to access or modify, or expose any data that does not belong to you; only test on your own account.
  • If you do access personal data belonging to someone else, stop straight away.
  • Do not execute, or attempt to execute, a Denial of Service (DoS) attack.
  • Do not run any automated tools against our servers without prior coordination.
  • Do not exfiltrate data from our infrastructure (including source code, data backups, configuration files).
  • If you obtain remote access to our system, report your finding immediately.
  • Avoid scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site).
  • Keep within the guidelines of our Terms & Conditions .
  • Keep details of vulnerabilities secret until Bookwhen has been notified and had a reasonable amount of time to fix the vulnerability.

Not accepted

  • Volumetric vulnerabilities are not in scope
  • TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS 1.0 support, are not in scope.
  • Functional bugs that do not create a security vulnerability are not in scope.

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.