BoursoBank Bug Bounty Program
BoursoBank, a subsidiary of Société Générale, is a pioneer and leader in online banking and financial information in France.
Reward
Program
Hacktivity
👋 INTRODUCTION
Welcome to the BoursoBank Bug Bounty program!
BoursoBank, a subsidiary of Société Générale, is a pioneer and leader in online banking and financial information in France. Its mission is to simplify banking, empower its customers and give everyone the ability to take control of their finances.
BoursoBank has over 9.4 million customers in France and offers a wide range of 61 products and services to meet customers’ banking needs: day-to-day banking and payments, savings, investments, trading, loans, insurance and money-saving tips.
Its information portal, www.boursorama.com, is ranked as the leading digital brand in the economy and finance sector, with an average of 136 million visits per month in 2025. BoursoBank is also an employer committed to sustainable development and CSR, certified B Corp.
Sharing your data and carrying out all your transactions via digital channels requires absolute trust in your banking partner. That is why the security of our application and of our networks is a top priority for BoursoBank.
We're excited to offer a way for the security community to help us find and fix vulnerabilities on our platform.
📋 Program Rules
Testing Policy and Responsible Disclosure
Please adhere to the following rules while performing research on this program:
- Denial of service (DoS) attacks on BoursoBank applications, servers, networks or infrastructure are strictly forbidden.
- Avoid tests that could cause degradation or interruption of our services.
- Do not use automated scanners or tools that generate large amounts of network traffic. Use automated tools gently, with a maximum of 10 requests per second.
- Do not leak, copy, manipulate or destroy any user data or files in any of our applications or servers.
- No vulnerability disclosure, full, partial or otherwise, is allowed.
- Make sure to follow the User-Agent requirements below.
We ask that you conduct your bug bounty activities in a way that does not impact the experience of our customers. If you are interested in testing something that may be considered dangerous, we encourage you to contact us, and we will work with you to provide the necessary testing conditions.
We strive to provide optimal testing conditions (e.g. no VPN required), but failure to adhere to the stated precautions and causing business issues will result in disqualification from the bug bounty program without reward.
🏷️ User-Agent Requirements and Exemption
Add the -BugBounty-boursobank-31337 string to the User-Agent header in your requests. This is important because, if your traffic impacts the quality of our services, we will temporarily block bug bounty requests based on this User-Agent.
The specific User-Agent is required for heavy traffic. However, for lighter traffic when searching for bugs, it is acceptable to temporarily use a regular User-Agent if you believe the specific User-Agent has an impact on your research. This must remain exceptional.
⚠️ Important Precautions and Limitations
As a complement to the program’s rules and testing policy:
- DO NOT alter compromised accounts by creating, deleting or modifying any data.
- DO NOT use compromised accounts to search for post-authentication vulnerabilities, as these will not be eligible.
- DO NOT include Personally Identifiable Information (PII) in your report. Please REDACT/OBFUSCATE any PII that is part of your PoC (screenshots, server responses, JSON files, etc.) as much as possible.
- In case of exposed credentials or secrets, limit yourself to verifying their validity.
- In case of a sensitive information leak, DO NOT extract or copy every exposed document or piece of data. Limit yourself to describing and listing what is exposed.
💰 Reward Eligibility
We are happy to thank everyone who submits valid reports which help us improve the security of BoursoBank. However, only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the initial discoverer of a vulnerability, and the vulnerability must not have been previously detected in our internal vulnerability tracking system.
- The vulnerability must be a qualifying vulnerability.
- You must not break any of the testing policy rules listed above.
- You must not be a former or current employee of BoursoBank or one of its contractors.
- The report must contain the following elements:
- A clear textual description of the vulnerability, how it can be exploited, its security impact on the application, its users and BoursoBank, and remediation advice.
- Proof of exploitation: screenshots demonstrating that the exploit was performed and showing the final impact.
- Complete steps with the necessary information to reproduce the exploit, including, if necessary, code snippets, payloads and commands.
Reward amounts are based on:
- The reward grid for the report’s scope.
- CVSS scoring and the actual business impact of the vulnerability, as assessed through risk analysis.
Reward
| Asset value | CVSS | CVSS | CVSS | CVSS |
|---|---|---|---|---|
| €100 | €500 | €1,500 | €3,000 | |
| €50 | €300 | €800 | €1,500 |
Systemic issues
We appreciate all valid reports submitted to our program that enhance our security. However, please note that if a similar issue (see definition in 'More info') has already been reported, by you or any other hunter, the reward will be decreasing according to these percentages.
Scopes
| Scope | Type | Asset value | Expand rewards grid |
|---|---|---|---|
https://play.google.com/store/apps/details?id=com.boursorama.android.clients | Mobile application Android | ||
Low Medium High Critical | |||
https://apps.apple.com/fr/app/boursobank/id425368900 | Mobile application IOS | ||
Low Medium High Critical | |||
api.boursobank.com | API | ||
Low Medium High Critical | |||
clients.boursobank.com | Web application | ||
Low Medium High Critical | |||
tradingboard.boursobank.com | Web application | ||
Low Medium High Critical | |||
www.boursobank.com | Web application | ||
Low Medium High Critical | |||
Out of scopes
- All domains or subdomains not listed in the above list of 'Scopes'
Vulnerability types
Qualifying vulnerabilities
- SQL Injection (SQLi)
- Remote Code Execution (RCE)
- Insecure Direct Object Reference (IDOR) with unauthorized access to other users' data
- Horizontal and vertical privilege escalation
- Authentication bypass and broken authentication mechanisms
- Local and remote file access vulnerabilities (LFI, RFI, XXE, SSRF, XSPA)
- Cross-Origin Resource Sharing (CORS) with demonstrated access to sensitive data from an attacker-controlled origin
- Open Redirect with demonstrated phishing, token leakage, or security impact
- Exposed secrets, credentials or sensitive information allowing unauthorized access, privilege escalation or access to other users' data
- Enumeration of BoursoBank customers at scale with confirmed valid accounts (login, email, phone number, PII)
- Tabnabbing with realistic user compromise or phishing impact
- Malicious file upload leading to exploitation
- Ability to spam other users at scale with demonstrated bypass of abuse controls (email, SMS, messaging systems)
- Misconfigured or exposed API keys leading to unauthorized usage or abuse
- Cross-site Request Forgery (CSRF) with demonstrated unauthorized actions
- Influencing and changing the AI model in ways that impact other users
- Ability to perturb valid inputs such that the model produces incorrect outputs for other users
- Circumventing history protections and accessing other users' data or history
- Accessing or revealing internal prompts, model behavior or confidential system information
- Ability to poison or tamper with the AI model, its data, or its architectureBroken Link or Social media hijacking without account takeover
- Exposed secrets, credentials or sensitive information from an asset under our control and affecting at least one of our scopes
Non-qualifying vulnerabilities
- Cross-Site Scripting (XSS) impacting other users
- Business Logic Errors vulnerability with real security impact
- Missing cookie flags without exploitation
- Content or text injections without security impact
- Clickjacking or UI redressing without impact
- Denial of Service (DoS) attacks
- Recently disclosed CVEs (less than 30 days) without exploitation
- CVEs without exploitable vulnerability and proof of concept
- Open ports or services without exploitable vulnerability
- Social engineering of staff or contractors
- Presence of autocomplete attribute on forms
- Vulnerabilities affecting outdated browsers or platforms
- Self-XSS or XSS affecting only the reporter
- Any hypothetical issue or best practice without proof of exploitation
- SSL/TLS issues or best practices without impact
- Unexploitable vulnerabilities (e.g. header-based XSS, non-impactful Open Redirect)
- Reports requiring MITM or physical access to a victim device
- Missing security headers without direct exploitation
- Low impact CSRF (e.g. logout, unauthenticated actions, preference changes)
- Invalid or missing email security records (SPF, DKIM, DMARC)
- Session management issues without account takeover, privilege escalation or unauthorized actions
- Disclosure of information without exploitable impact (stack traces, paths, versions, IPs, directory listings, EXIF metadata, feature flags, configuration names)
- Presence of public, expired or unusable tokens or keys without demonstrated unauthorized access or abuse (e.g. DEFAULT_JWT or JAVASCRIPT_APPS_BEARER)
- CSV injection without exploitation
- HTTP Strict Transport Security (HSTS) issues
- Subdomain takeover without full exploitable impact
- Blind SSRF without exploitable impact (e.g. DNS or HTTP callbacks only)
- Lack or bypass of rate-limiting, brute force or captcha without compromise or large-scale abuse
- User enumeration without confirmed valid accounts or without scalability
- Weak password policies (length, complexity, reuse)
- Password reset token leakage without exploitation
- Stolen secrets or credentials from third-party assets not under our control
- Pre-account takeover scenarios (e.g. OAuth edge cases)
- GraphQL introspection enabled without unauthorized access or privilege escalation
- Task Hijacking
- Lack of client-side protections on mobile binaries: SSL pinning/binary protection/code obfuscation/jailbreak detection/root detection/anti-debugging controls/etc
- Lack of encryption on internal databases/preference files on mobile device
- Generic Android or iOS vulnerabilities
- Exploits that are only possible on Android versions that are not currently supported at the time of the emission of the vulnerability report
- Exploits that are only possible on iOS versions that are not currently supported at the time of the emission of the vulnerability report
- Exploits that are only possible on a jailbroken/rooted device
- Crashing your own application
- Open Redirect via Reflected XSS payload
- AI prompt injection affecting only the reporter
- AI model hallucinations or false data disclosure
- AI outputs that are inaccurate, offensive or misleading without security impact
- Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
- Exposed secrets, credentials or information on an asset under our control that are not applicable to the program's scope
Reports of leaks and exposed credentials
In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and policy. To summarize our policy, you may refer to the below table:
Hunting requirements
Account access
Self-register
You are allowed to test the authenticated part of the platform but no tests accounts are provided. You are free to create an account or use your existing personal account if you already have one. Note however that no refund will be done through this program. Be extra careful on your actions with your account, as we can’t promise to fix issues you might cause yourself.
User agent
Please append to your user-agent header the following value: ' -BugBounty-boursobank-31337 '.
Hunters collaboration
When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.
For more information, see help center.
Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.