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)

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
Submissions validated outside of this may be awarded a €25 bonus.

This remains at the discretion of Flywire to award.

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.

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

This program follows Intigriti's triage standards

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.