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

Cedars-Sinai

By Cedars-Sinai Medical Center Vulnerability disclosure program on HackerOne cedars-sinai.edu

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
39
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 1 day
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Response
Within 1 days | First Response | 1 days |
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

39 assets you may test.

Wildcard domains 39

  • *appofchoice.huntingtonhospital.com Critical No bounty
  • *apps.huntingtonhospital.com Critical No bounty
  • *cedars-sinai.edu Critical No bounty
  • *cedars-sinai.org Critical No bounty
  • *csmc.edu Critical No bounty
  • *hhapps.net Critical No bounty
  • *hhcareers.com Critical No bounty
  • *hhec.org Critical No bounty
  • *hhphysicians.org Critical No bounty
  • *hmh-direct.com Critical No bounty
  • *hmhdr.com Critical No bounty
  • *hmhdr.net Critical No bounty
  • *hmhdr.org Critical No bounty
  • *hmhrx.com Critical No bounty
  • *hmhrx.net Critical No bounty
  • *hmhrx.org Critical No bounty
  • *hmtest.org Critical No bounty
  • *huntingtonhealtheconnect.com Critical No bounty
  • *huntingtonhealtheconnect.net Critical No bounty
  • *huntingtonhealth.net Critical No bounty
  • *huntingtonhealthnetwork.com Critical No bounty
  • *huntingtonhealthnetwork.net Critical No bounty
  • *huntingtonhospital.com Critical No bounty
  • *huntingtonhospital.net Critical No bounty
  • *huntingtonhospital.org Critical No bounty
  • *huntingtonrx.com Critical No bounty
  • *huntingtonrx.net Critical No bounty
  • *kerlanjobe.org Critical No bounty
  • *legacy.huntingtonhospital.org Critical No bounty
  • *mycslink.org Critical No bounty
  • *ourstory.huntingtonhospital.com Critical No bounty
  • *pricing.huntingtonhospital.com Critical No bounty
  • *sangabrielvalleyhealtheconnect.com Critical No bounty
  • *sangabrielvalleyhealtheconnect.net Critical No bounty
  • *sd.invio.dev Critical No bounty
  • *sgveconnect.com Critical No bounty
  • *sgveconnect.org Critical No bounty
  • *www.cshs.org Critical No bounty
  • *www.marinahospital.com Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Cedars-Sinai (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
  • contact us immediately if you inadvertently encounter user data;
  • do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to Cedars Sinai;
  • Comply with all applicable laws;
  • Do not violate any other law (other than those that would result only in claims by Cedars Sinai), or disrupt or compromise any data;

Not accepted

  • Denial of Service Attacks
  • Reports from automated tools or scans
  • Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
  • Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
  • Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
  • Self-exploitation (e.g., cookie reuse)
  • Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
  • Our policies on presence/absence of SPF / DMARC records
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
  • Social engineering of Cedars Sinai employees or contractors
  • Any physical attempt against Cedars Sinai property or data centers
  • Presence of autocomplete attribute on web forms
  • Missing secure cookie flags on non-sensitive cookies
  • Banner identification issues (e.g., identifying what web server version is used)
  • Open ports which do not lead directly to a vulnerability
  • Open redirect vulnerabilities
  • Publicly accessible login panels
  • Content spoofing / text injection
  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

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

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

If you have information related to security vulnerabilities of Cedars Sinai services, we want to hear from you. Please submit a report in accordance with the guidelines below. We value the positive impact of your work and thank you in advance for your contribution. Cedars-Sinai Medical Center looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Cedars-Sinai Medical Center will make a best effort to meet the following response targets for hackers participating in our program:

Type of Response SLA in business days
First Response 1 days
Time to Triage 2 days
Time to Resolution depends on severity and complexity

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

Program Rules

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
  • Do not cause harm to Cedars Sinai Health System, our customers, or others;
    • provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);
    • Do not compromise the privacy or safety of our customers and the operation of our services. Specifically;
    • contact us immediately if you inadvertently encounter user data;
    • do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to Cedars Sinai;
    • act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);
    • Comply with all applicable laws;
  • Do not violate any other law (other than those that would result only in claims by Cedars Sinai), or disrupt or compromise any data;
  • By submitting a report, you represent that you are not located in or otherwise ordinarily resident in Cuba, Iran, North Korea, Sudan, Syria or Crimea; and that you are not identified on, or owned or controlled by or acting on behalf of a party identified on, restricted party lists maintained by the U.S. or other relevant governments.

#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Denial of Service Attacks
  • Reports from automated tools or scans
  • Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
  • Missing best practices, information disclosures, use of known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
  • Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
  • Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
  • Self-exploitation (e.g., cookie reuse)
  • Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
  • Our policies on presence/absence of SPF / DMARC records
  • Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a Cedars-Sinai related account
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
  • Social engineering of Cedars Sinai employees or contractors
  • Any physical attempt against Cedars Sinai property or data centers
  • Presence of autocomplete attribute on web forms
  • Missing secure cookie flags on non-sensitive cookies
  • Banner identification issues (e.g., identifying what web server version is used)
  • Open ports which do not lead directly to a vulnerability
  • Open redirect vulnerabilities
  • Publicly accessible login panels
  • Content spoofing / text injection
  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Cedars-Sinai Medical Center and our users safe!

If you have information related to security vulnerabilities of Cedars Sinai services, we want to hear from you. Please submit a report in accordance with the guidelines below. We value the positive impact of your work and thank you in advance for your contribution. Cedars-Sinai looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Cedars-Sinai will make a best effort to meet the following response targets for hackers participating in our program:

Type of Response SLA in business days
First Response 1 days
Time to Triage 2 days
Time to Resolution depends on severity and complexity

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

Program Rules

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
  • Do not cause harm to Cedars Sinai Health System, our customers, or others;
    • provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);
    • Do not compromise the privacy or safety of our customers and the operation of our services. Specifically;
    • contact us immediately if you inadvertently encounter user data;
    • do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to Cedars Sinai;
    • act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);
    • Comply with all applicable laws;
  • Do not violate any other law (other than those that would result only in claims by Cedars Sinai), or disrupt or compromise any data;
  • By submitting a report, you represent that you are not located in or otherwise ordinarily resident in Cuba, Iran, North Korea, Sudan, Syria or Crimea; and that you are not identified on, or owned or controlled by or acting on behalf of a party identified on, restricted party lists maintained by the U.S. or other relevant governments.

#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Denial of Service Attacks
  • Reports from automated tools or scans
  • Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
  • Missing best practices, information disclosures, use of known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
  • Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
  • Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
  • Self-exploitation (e.g., cookie reuse)
  • Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
  • Our policies on presence/absence of SPF / DMARC records
  • Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a Cedars-Sinai related account
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
  • Social engineering of Cedars Sinai employees or contractors
  • Any physical attempt against Cedars Sinai property or data centers
  • Presence of autocomplete attribute on web forms
  • Missing secure cookie flags on non-sensitive cookies
  • Banner identification issues (e.g., identifying what web server version is used)
  • Open ports which do not lead directly to a vulnerability
  • Open redirect vulnerabilities
  • Publicly accessible login panels
  • Content spoofing / text injection
  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Cedars-Sinai and our users safe!