Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Mon Espace Santé (MES)

Bug bounty on YesWeHack monespacesante.fr

Accepting reports
Go to program
Top reward
€8,000
Top severity paid
Critical
Assets in scope
43
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to €8,000
for critical bugs, from €50.
Report on YesWeHack
Submit through the program page.
No public write-ups
Keep findings private.

Rewards

What YesWeHack lists as the payout for each severity.

Severity Reward
Critical €8,000
High €4,000
Medium €800
Low €200

Scope

43 assets you may test, 1 excluded.

Web 25

  • admincms.developer.monespacesante.fr
  • admincms.monespacesante.fr
  • adminstore.developer.monespacesante.fr
  • adminstore.monespacesante.fr
  • am.developer.monespacesante.fr
  • auth.monespacesante.fr
  • auth.preprod.monespacesante.fr
  • cms.monespacesante.fr
  • editeurs.developer.monespacesante.fr
  • editeurs.monespacesante.fr
  • fhir.developer.monespacesante.fr
  • fhir.monespacesante.fr
  • knowage.developer.monespacesante.fr
  • knowage.monespacesante.fr
  • preprod1.monespacesante.fr
  • preprod2.monespacesante.fr
  • preprod.auth.monespacesante.fr
  • preprod.monespacesante.fr
  • securite.monespacesante.fr
  • support.monespacesante.fr
  • wps-cps.dmp.monespacesante.fr
  • www.monespacesante.fr
  • www.preprod1.monespacesante.fr
  • www.preprod2.monespacesante.fr
  • www.preprod.monespacesante.fr

APIs 8

  • api.developer.monespacesante.fr
  • api.editeur.preprod.monespacesante.fr
  • api.monespacesante.fr
  • api.preprod.monespacesante.fr
  • editeur.api.monespacesante.fr
  • preprod.api.monespacesante.fr
  • preprod.editeur.api.monespacesante.fr
  • www.editeur.api.monespacesante.fr

Android apps 1

  • play.google.com/store/apps/details?id=fr.assurancemaladie.monespacesante&showAllReviews=true (Android)

iOS apps 1

  • apps.apple.com/fr/app/mon-espace-sant%C3%A9/id1589255019 (iOS)

Products and areas 8

  • am.editeur.preprod.monespacesante.fr
  • am.monespacesante.fr
  • am.preprod.monespacesante.fr
  • editeur.am.monespacesante.fr
  • preprod.am.monespacesante.fr
  • preprod.editeur.am.monespacesante.fr
  • www.am.monespacesante.fr
  • www.editeur.am.monespacesante.fr
Out of scope (1)
  • Anything that is not explicitely listed as part of the Scope

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Mon Espace Santé (MES) (via YesWeHack)'s policy. "We" in these lines means the program, not this site.

While testing

  • Denial of service (DoS) attacks on our 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 amount of network traffic.
  • Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
  • Do not copy any files from our applications/servers and disclose them.
  • No vulnerability disclosure, full, partial or otherwise, is allowed.
  • You must be the first reporter of a vulnerability.
  • You must not be a former or current employee of our organisation or one of its contractors.

Not accepted

  • Broken Link/Social media Hijacking
  • Tabnabbing
  • Missing cookie flags
  • Content/Text injections
  • Clickjacking/UI redressing
  • Denial of Service (DoS) attacks
  • Recently disclosed CVEs (less than 30 days sinces patch release)
  • CVEs without exploitable vulnerabilities and PoC
  • Open ports or services without exploitable vulnerabilities and PoC
  • Social engineering of staff or contractors
  • Presence of autocomplete attribute on web forms
  • Vulnerabilities affecting outdated browsers or platforms
  • Self-XSS or XSS that cannot be used to impact other users
  • Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
  • SSL/TLS issues (e.g. expired certificates, best practices)
  • Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
  • Reports with attack scenarios requiring MITM or physical access to victim's device
  • Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
  • Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
  • Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
  • Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
  • CSV injection
  • Malicious file upload (e.g. EICAR files, .EXE)
  • HTTP Strict Transport Security Header (HSTS)

Summarised with AI from the program policy on YesWeHack, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 7 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.

  1. Scope added

    Anything that is not explicitely listed as part of the Scope (out of scope)

  2. Scope added

    am.monespacesante.fr

  3. Scope added

    www.editeur.am.monespacesante.fr

  4. Scope added

    www.am.monespacesante.fr

  5. Scope added

    preprod.editeur.am.monespacesante.fr

  6. Scope added

    preprod.am.monespacesante.fr

  7. Scope added

    am.preprod.monespacesante.fr

  8. Scope added

    am.editeur.preprod.monespacesante.fr

  9. Scope added

    editeur.am.monespacesante.fr

  10. Scope added

    www.editeur.am.monespacesante.fr

  11. Scope added

    www.am.monespacesante.fr

  12. Scope added

    preprod.editeur.am.monespacesante.fr

  13. Scope added

    preprod.am.monespacesante.fr

  14. Scope added

    am.preprod.monespacesante.fr

  15. Scope added

    am.editeur.preprod.monespacesante.fr

  16. Scope added

    editeur.am.monespacesante.fr

  17. Scope added

    am.monespacesante.fr

  18. Scope added

    wps-cps.dmp.monespacesante.fr

  19. Scope added

    admincms.developer.monespacesante.fr

  20. Scope added

    adminstore.developer.monespacesante.fr

  21. Scope added

    knowage.developer.monespacesante.fr

  22. Scope added

    editeurs.developer.monespacesante.fr

  23. Scope added

    fhir.developer.monespacesante.fr

  24. Scope added

    api.developer.monespacesante.fr

  25. Scope added

    am.developer.monespacesante.fr

  26. Scope added

    fhir.monespacesante.fr

  27. Scope added

    play.google.com/store/apps/details?id=fr.assurancemaladie.monespacesante&showAllReviews=true (Android)

  28. Scope added

    apps.apple.com/fr/app/mon-espace-sant%C3%A9/id1589255019 (iOS)

  29. Scope added

    www.editeur.api.monespacesante.fr

  30. Scope added

    www.preprod2.monespacesante.fr

  31. Scope added

    www.preprod1.monespacesante.fr

  32. Scope added

    www.preprod.monespacesante.fr

  33. Scope added

    securite.monespacesante.fr

  34. Scope added

    preprod2.monespacesante.fr

  35. Scope added

    preprod1.monespacesante.fr

  36. Scope added

    preprod.monespacesante.fr

  37. Scope added

    preprod.editeur.api.monespacesante.fr

  38. Scope added

    preprod.auth.monespacesante.fr

  39. Scope added

    preprod.api.monespacesante.fr

  40. Scope added

    auth.preprod.monespacesante.fr

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search 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 yeswehack.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Rules

My Health Space

It is an individual digital space, a Virtual Health Notebook, which is open to all French people from the beginning of 2022.

It allows:

  • To store its health data online and replaces the shared medical record (DMP).
  • Keep and file all medical documents.

It also contains:

  • Secure messaging with an address to converse with healthcare professionals.
  • An agenda for medical appointments and other acts.
  • A catalog of applications.
  • The data collected by the connected objects on the condition that the applications used are referenced, that they meet all the security conditions imposed by the French State.
  • Your children's health profiles can be integrated into it.

This site is accessible to all and compatible with all terminals (smartphones, tablets, computers). The Caisse Nationale d'Assurance Maladie (CNAM) and the French Ministry of Solidarity and Health are committed to ensuring the protection, confidentiality and security of all data (administrative and health). Its security and the protection of personal data are guaranteed by the French State, the CNIL, and the CNAM. Their accommodation is provided in France. Among the features, some have a critical aspect for the application.

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 our 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 amount of network traffic.
  • Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
  • Do not copy any files from our applications/servers and disclose them.
  • No vulnerability disclosure, full, partial or otherwise, is allowed.

Reward Eligibility and Amount

We are happy to thank everyone who submits valid reports which help us improve our security, however only those that meet the following eligibility requirements may receive a monetary reward:

  • You must be the first reporter of a vulnerability.
  • The vulnerability must be a qualifying vulnerability (see below).
  • The report must contain the following elements:
    • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and our organisation, and remediation advice on fixing the vulnerability
    • Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
    • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
  • You must not break any of the testing policy rules listed above.
  • You must not be a former or current employee of our organisation or one of its contractors.
  • If you find the same vulnerability several times, please create only one report and eventually use comments. You'll be rewarded according to your findings.

Reward amounts are based on:

  • Reward grid of the report's scope
  • CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Out of scope

  • Anything that is not explicitely listed as part of the Scope

Qualifying vulnerabilities

  • SQL Injection (SQLi)
  • Cross-Site Scripting (XSS)
  • Remote Code Execution (RCE)
  • Insecure Direct Object Reference (IDOR)
  • Horizontal and vertical privilege escalation
  • Authentication bypass & broken authentication
  • Business Logic Errors vulnerability with real security impact
  • Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
  • Cross-Origin Resource Sharing (CORS) with real security impact
  • Cross-site Request Forgery (CSRF) with real security impact
  • Open Redirect
  • Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes

Non-qualifying vulnerabilities

  • Broken Link/Social media Hijacking
  • Tabnabbing
  • Missing cookie flags
  • Content/Text injections
  • Clickjacking/UI redressing
  • Denial of Service (DoS) attacks
  • Recently disclosed CVEs (less than 30 days sinces patch release)
  • CVEs without exploitable vulnerabilities and PoC
  • Open ports or services without exploitable vulnerabilities and PoC
  • Social engineering of staff or contractors
  • Presence of autocomplete attribute on web forms
  • Vulnerabilities affecting outdated browsers or platforms
  • Self-XSS or XSS that cannot be used to impact other users
  • Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
  • SSL/TLS issues (e.g. expired certificates, best practices)
  • Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
  • Reports with attack scenarios requiring MITM or physical access to victim's device
  • Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
  • Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
  • Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
  • Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
  • Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
  • CSV injection
  • Malicious file upload (e.g. EICAR files, .EXE)
  • HTTP Strict Transport Security Header (HSTS)
  • Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
  • Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
  • Lack or bypass of rate-limiting, brute-forcing or captcha issues
  • User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
  • Weak password policies (e.g. length, complexity, reuse)
  • Ability to spam users (email / SMS / direct messages flooding)
  • Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
  • Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
  • Pre-account takeover (e.g. account creation via oAuth)
  • GraphQL Introspection is enabled
  • Task Hijacking
  • Crashing your own application
  • 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
  • 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
  • Generic Android or iOS vulnerabilities
  • 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
  • GraphQL queries containing (multiple) statements that may cause Denial of Service (DoS) attacks