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

Nexuzhealth Web PACS

Bug bounty on Intigriti nexuzhealth.be

Accepting reports Full safe harbor
Go to program
Top reward
€1,000
Top severity paid
Critical
Assets in scope
3
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to €1,000
for critical bugs.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.

Rewards

What Intigriti lists as the payout for each severity.

Severity Reward
Critical €1,000 from €850
High €400
Medium €100

Scope

3 assets you may test.

Web 3

  • idp-contact.nexuzhealth.be
  • idp-url.nexuzhealth.be
  • media.nexuzhealth.be/patient

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Nexuzhealth Web PACS (via Intigriti)'s policy.

While testing

  • Please do not DDOS these logins and don’t try to guess other codes, ... . The usernames will automatically be locked!
  • XSS (no self-xss and only on latest versions of browsers)

Not accepted

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • 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.)
  • Clickjacking without proven impact/unrealistic user interaction
  • 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

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

Changes

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

    idp-url.nexuzhealth.be

  2. Scope removed

    idp-contact.nexuzhealth.be

  3. Scope removed

    media.nexuzhealth.be/patient/

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

Description

This website is used to provide patient access to their radiology images (PACS).

Patients logon with their date of birth, and a unique code provided to them by the physician. This code provides access to one study.

Rules of engagement

For this project, we are bound to 3rd-party closed-source software for some parts. Please be aware that we will not be able to fix all bugs internally, and may have to await other vendors.

In scope

We are particularly interested, but not limited to, find out how one can exploit our system to:

  • Horizontal or vertical privilege escalation
  • XSS (no self-xss and only on latest versions of browsers)
  • RCE
  • SQL injection
  • …

Out of scope

Any area that is not explicitly listed in the section above is out of scope. The areas that are out of scope include, but are not limited to, the following:

Application

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • 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.)
  • Clickjacking without proven impact/unrealistic user interaction
  • 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
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks are not sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven business impact

General

  • 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

Severity

It will be the responsibility of intigriti to pay ethical hackers in a timely and legal way. Payouts will only take place after agreement with UZ Leuven on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.

Duplicates policy: When two identical issues are reported, with different endpoints being the only difference between submissions, only the first submission will have the criticality below assigned. If similar reports by the same user are reported within 14 days after accepting the previous (only differentiating in endpoint), the reports will be accepted but in a lower criticality and hence impact the bounty.

Rewards in this project are categorised according to impact, not according to attack vector.

Exceptional

  • Remote Code Execution
  • Access to all patient records
  • Access to specific patient record (for instance you want to obtain data for patient X and you are able to)

Critical

  • Access to random patient record

High

  • Service disruption (e.g. config change)

Medium

  • Compomise of one user, with user interaction required (Reflective XSS)

FAQ

Can we use test accounts?

The following login data can be used to test the platform.

  • Patient 1: Code: e3Dgin2r D.o.B: 05/09/1967

  • Patient 2: Code: mcuk7jp4 D.o.B: 01/05/1967

Please do not DDOS these logins and don’t try to guess other codes, ... . The usernames will automatically be locked!