- Top reward
- Not published
- 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.
- 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.
- Pays cash
-
Yes
Our monetary rewards are loosely consistent with other known reward programs and the final amount is always chosen at the discretion of our reward panel.
- Safe harbor
-
Partial
Please perform your research in good faith. Please don’t publicly disclose a vulnerability without our consent and review.
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.
Domains 1
- airwallex.com
Wildcard domains 1
- *.airwallex.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Airwallex's policy. "We" in these lines means the program, not this site.
While testing
-
Please do not attempt to carry out DoS or DDoS attacks, social engineering, spamming or do other similarly questionable things.
-
When investigating a vulnerability, please only ever target your own accounts.
-
Never attempt to access anyone else's data and do not engage in any activity that would be disruptive or damaging to the users or to Airwallex.
-
If you come across user information during the course of your research, do not save, store, copy, transfer, disclose, or otherwise retain this information
-
Please don’t publicly disclose a vulnerability without our consent and review.
-
your testing must not violate any law, or disrupt or compromise any data that is not your own.
Not accepted
-
The use of automated scanners is strictly prohibited.
-
Disclosure of known public files or directories, (e.g. robots.txt).
-
Clickjacking and issues only exploitable through clickjacking.
-
CSRF on forms that are available to anonymous users (e.g. the contact form).
-
CSRF attacks that require knowledge of the CSRF token (e.g. attacks involving a local machine).
-
Logout Cross-Site Request Forgery (logout CSRF).
-
Content Spoofing.
-
Login or Forgot Password page brute force and account lockout not enforced.
-
OPTIONS HTTP method enabled.
-
Username / email enumeration.
-
Missing HTTP security headers
-
HTTP/DNS cache poisoning.
-
SSL/TLS Issues
-
Self-XSS reports will not be accepted.
-
Missing or incorrect SPF records of any kind.
-
Missing or incorrect DMARC records of any kind.
-
Source code disclosure vulnerabilities.
-
Information disclosure of non-confidential information
-
Email bombing/flooding/rate limiting
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.