Skip to content

CareEvolution

Bug bounty on Self-hosted careevolution.com

Accepting reports Full safe harbor
Top reward
Not published
Top severity paid
Not published
Assets in scope
16
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.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
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 CareEvolution has established a bug bounty program to incentivize security researchers to identify and report security vulnerabilities or bugs in our systems.
Response
Within 5 days If you include your email address in your report, you will receive a response from us within five business days acknowledging receipt of your report.
Safe harbor
Full If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

16 assets you may test, 2 excluded.

Domains 10

  • careevolutionapi.com
  • careevolutionapps.com
  • careevolution.com
  • designer.mydatahelps.org
  • mydatahelps.org
  • myfhr.careevolution.com
  • rosetta.careevolution.com
  • share.careevolution.com
  • symptomshark.org
  • the careevolution.com website

Wildcard domains 3

  • *.careevolutionapi.com
  • *.careevolutionapps.com
  • *.symptomshark.org

APIs 2

  • api.designer.mydatahelps.org
  • api.mydatahelps.org

Products and areas 1

  • MyDataHelps and myFHR mobile applications
Out of scope (2)
  • Any service not expressly listed above, such as any connected services
  • vulnerabilities found in systems from our vendors

Rules

What the policy asks of you, and the bug types it won't reward, quoted from CareEvolution's policy. "We" in these lines means the program, not this site.

While testing

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence.
  • Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not include Protected Health Information (PHI), Personally Identifiable Information (PII), or any other sensitive data
  • Do not join any projects other than Symptom Shark or test projects that you have created for yourself using https://designer.mydatahelps.org
  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing

Not accepted

  • Vulnerabilities that rely on guessing a UUID or identifier of similar entropy without a demonstrated leak vector
  • Disclosure of publicly known files or directories (e.g., robots.txt)
  • Issues only exploitable through clickjacking
  • CSRF vulnerabilities on forms accessible to unauthenticated users
  • CSRF attacks requiring knowledge of CSRF tokens (e.g., involving local machines)
  • Logout CSRF vulnerabilities
  • Content spoofing
  • Brute force attacks on login or password recovery pages without account lockout enforcement
  • OPTIONS HTTP method enabled
  • Username/email enumeration
  • Missing HTTP security headers
  • HTTP/DNS cache poisoning
  • Self-XSS reports, and any XSS vulnerabilities where local access is required
  • Missing or incorrect records related to SPF, DMARC, MTA-STS or other emerging standards
  • Source code disclosure vulnerabilities
  • Information disclosure of non-confidential information
  • Email bombing/flooding/rate limiting
  • DoS/DDoS attacks
  • Physical intrusion
  • CORS issues or cookie attributes on sites containing only public content
  • Regular expression denial of service (ReDoS)
  • Presence of Exif metadata on images
  • Lack of CAPTCHA or rate limiting
  • Software version disclosure

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.