- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
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.
- Safe harbor
-
Partial
Keep details of vulnerabilities secret until Zapier has been notified and had a reasonable amount of time to fix 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, 6 excluded.
Domains 1
- zapier.com
Out of scope (6)
- community.zapier.com
- go.zapier.com
- help.zapier.com
- opens.zapier.com
- platform.zapier.com
- status.zapier.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Zapier's policy. "We" in these lines means the program, not this site.
While testing
-
Access or expose only customer data that is your own.
-
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. Do not attempt to pivot to other servers or elevate access.
-
Avoid scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site). This includes the spamming of contact forms, support emails, etc.
-
Keep within the guidelines of our Terms of Service.
-
Keep details of vulnerabilities secret until Zapier has been notified and had a reasonable amount of time to fix the vulnerability.
Not accepted
-
Information leakage that cannot be used to make a direct attack, like server IP, server version, path, error message, internal IP, etc.
-
PII - do not collect any personally identifiable information - including credit card information, addresses and phone numbers from other customers.
-
Reports from automated tools or scans that are not validated
-
Attacks against Zapier infrastructure
-
Social engineering and physical attacks
-
Distributed Denial of Service attacks that require large volumes of data.
-
0-day vulnerabilities less than 60 days from patch release are ineligible for bounty.
-
Provisioning and/or usability issues.
-
Violations of licenses or other restrictions applicable to any vendor's product.
-
Security vulnerabilities in third-party products or websites that are not under Zapier’s direct control.
-
Fingerprinting / banner disclosure / server versions on public services
-
"Self" XSS
-
Not verifying email at signup
-
DNSSEC
-
Unchained open redirects
-
Content Spoofing
-
Missing cookie flags
-
SSL/TLS best practices
-
Mixed content warnings
-
Clickjacking/UI redressing without proof of exploitability
-
Highly speculative reports about theoretical damage
-
Feedback, comment, message, etc. flooding
-
SMS/Email flooding for some of our business
-
Disclosure of known public files or directories, (e.g., robots.txt)
-
Use of known-vulnerable library without proof of exploitability
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 6 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.