- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 5
- 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 as the policy says
- The policy page explains how.
- 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.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
For accepted reports we may provide a financial reward.
- Response
-
Within 5 days
We will respond to an accepted report within 5 business days with our evaluation of the report.
- Safe harbor
-
Full
If you have followed the instructions above, we will not take any legal action against you in regard to the report or pass on your personal details to third parties without your permission.
- Hall of fame
-
Yes
In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
5 assets you may test, 16 excluded.
Web 3
- The Portals web application
- The wetransfer.com web application
- WePresent
Domains 1
- wetransfer.com
iOS apps 1
- The iOS and Android WeTransfer applications
Out of scope (16)
- Ability to upload or download malicious files via wetransfer.com
- Authentication (or lack thereof) on free transfers
- Collect , both the web and mobile applications
- Distributed Denial of Service attacks (DDoS)
- Integrations and extensions created by third-party developers using our public API
- Missing security headers or 'best practices' (except if you are able to demonstrate a vulnerability that makes use of their absence)
- Non-production environments across our product line
- Paper
- Paste , both the web and mobile applications
- Policies as opposed to implementations - email verification, password length, or reuse, etc.
- Social engineering attacks
- Spam (unless a specific vulnerability leads to easily sending spam)
- Third party applications we make use of, but do not control. (e.g., a blog hosted on an external service - unless we've configured the blog in such a way as to make our in-scope areas vulnerable)
- Users hosting malware on our service (contact support for this)
- Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on wetransfer.com or related apps).
- Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from WeTransfer's policy. "We" in these lines means the program, not this site.
While testing
-
Submit your findings by using our Responsible Disclosure Form hosted by HackerOne.
-
Do not take advantage of the vulnerability or problem you have discovered, for example, by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
-
Do not reveal the problem to others until it has been resolved.
-
Do not use attacks on physical security, social engineering, distributed denial of service (or any attack using large volumes of requests), spam, or applications of third parties.
-
Please provide sufficient information to reproduce the problem so we can resolve it as quickly as possible.
Not accepted
-
Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts)
-
Policies as opposed to implementations - email verification, password length, or reuse, etc.
-
Ability to upload or download malicious files via wetransfer.com
-
Users hosting malware on our service (contact support for this)
-
Spam (unless a specific vulnerability leads to easily sending spam)
-
Authentication (or lack thereof) on free transfers
-
Missing security headers or 'best practices' (except if you are able to demonstrate a vulnerability that makes use of their absence)
-
Distributed Denial of Service attacks (DDoS)
-
Social engineering attacks
-
Integrations and extensions created by third-party developers using our public API
-
Non-production environments across our product line
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.