Flywire Vulnerability Disclose Program
By Flywire Vulnerability disclosure program on Intigriti flywire.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 32
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
- Pays cash
-
No
While we do not offer bounties for reported vulnerabilities, we deeply appreciate your contribution to securing our systems.
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
32 assets you may test.
Wildcard domains 32
- *.chrtpy.com
- *.cohortarrivals.com
- *.cohortflow.com
- *.cohortgoapp.com
- *.cohortgo.com
- *.cohort.link
- *.cohortpay.com
- *.flywire.com
- *.flywire.io
- *.flywire.tech
- *.invoiced.com
- *.myonplanhealth.com
- *.myonplanu.com
- *.onplanhealth.com
- *.onplanu.com
- *.oshcaustralia.com
- *.oshcaustralia.com.au
- *.oshc.info
- *.ovhcinsurance.com
- *.ovhcinsurance.com.au
- *.peertransfer.com
- *.simplee.com
- *.simpleepay.com
- *.studylink.com
- *.studylink.com.au
- *.unipaylive.com
- *.wpm-education.com
- *.wpm-education.co.uk
- *.wpm-pay.com
- *.wpm-pay.co.uk
- *.wpm-payment.com
- *.wpm-payment.co.uk
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Flywire Vulnerability Disclose Program (via Intigriti)'s policy.
While testing
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
-
The program follows a strict black-box approach: no credentials, internal documentation, or test environments will be provided.
-
All testing must be conducted against production systems as accessed by unauthenticated or standard users, if the application allows to sign-up.
-
No internal access or test accounts will be granted.
Not accepted
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that can't be used to exploit other users
-
Verbose messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration
-
Missing cookie flags
-
Missing security headers
-
Missing best practices in SSL/TLS configuration
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits.
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Any kind of Clickjacking
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Tokens leaked to third parties
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection without being able to modify the HTML
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homograph attacks
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
-
Not stripping metadata of files
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 43 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Status
Program status changed
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.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Hi bug hunters!
Flywire is a global payment solutions company that specializes in providing streamlined payment processes for international transactions in various industries, including education, healthcare, and travel. The company offers a platform that facilitates cross-border payments, allowing individuals and organizations to make and receive payments in different currencies.
We would like you to help us make Flywire an even more secure company.
Rules of engagement
By participating in this program, you agree to:
- Respect the Community Code of Conduct
- Respect the Intigriti Terms and Conditions
- Respect the scope of the program
- Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
You may not participate in this program if you are ordinarily resident in, or located in, any country or region subject to comprehensive sanctions, or if you are an individual or entity identified on any applicable sanctions list (including those administered by OFAC, the EU, the UN, or the UK's OFSI).
Validation times
We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
| Vulnerability Severity | Time to validate |
|---|---|
| Exceptional | 2 Working days |
| Critical | 2 Working days |
| High | 5 Working days |
| Medium | 15 Working days |
| Low | 15 Working days |
In scope
Introduction
We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!
Please review the domains in scope. Few of them may be redirections to the main site or specific services. This includes:
- Web applications
- Public APIs
- Subdomains
- Cloud-exposed services (e.g., S3 buckets etc.)
Any valid finding that aligns with the private Bug Bounty Program scope will be rewarded according to its payout levels.
Our worst-case scenarios are:
- Payment fraud. Posibility to make payments by adjusting the amount.
- PII or PHI leakage. Sensitive information of clients.
Any useful infrastructure information:
- All of our infrastructure is located in AWS. There is a Cloudflare WAF that should block any common attack or rate-limit automated request.
- The program follows a strict black-box approach: no credentials, internal documentation, or test environments will be provided. All testing must be conducted against production systems as accessed by unauthenticated or standard users, if the application allows to sign-up.
- No internal access or test accounts will be granted. Researchers are expected to interact with publicly exposed services under real-world conditions, without any privileged insight into internal architecture or source code.
Feedback Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program feedback link Please note this form will be checked periodically and should not be used for submission or support queries.
Out of scope
Every domain that is not in scope is considered out of scope Any other recipient will be considered out of scope.
Out of Scope Application vulnerabilities
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that can't be used to exploit other users
- Verbose messages/files/directory listings without disclosing any sensitive information
- CORS misconfiguration
- Missing cookie flags
- Missing security headers
- Missing best practices in SSL/TLS configuration
- Cross-site Request Forgery with no or low impact
- Presence of autocomplete attribute on web forms
- Reverse tabnabbing
- Bypassing rate-limits or the non-existence of rate-limits.
- Best practices violations (password complexity, expiration, re-use, etc.)
- Any kind of Clickjacking
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, etc.)
- Tokens leaked to third parties
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection without being able to modify the HTML
- Username/email enumeration
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- Banner grabbing/Version disclosure
- Not stripping metadata of files
- Same-site scripting
General vulnerabilities
- In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
- Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
- Spam, social engineering and physical intrusion
- DoS/DDoS attacks or brute force attacks
- Vulnerabilities that only work on software that no longer receive security updates
- Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
- Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
- Reports that state that software is out of date/vulnerable without a proof-of-concept
Severity
This program follows Intigriti's triage standards
FAQ
Where can we get credentials for any app?
You can self-register on the application but please don’t forget to use your @intigriti.me address.
Rewards
While we do not offer bounties for reported vulnerabilities, we deeply appreciate your contribution to securing our systems.
Moreover, if a vulnerability also falls within the scope of one of our private programs, we will provide a bonus equivalent to the bounty amount, ensuring fair compensation for your efforts.