eHealth Hub VZN KUL
By VZNKUL (Vlaams Ziekenhuis Netwerk KU Leuven) Bug bounty on Intigriti vznkul.be
- Top reward
- €2,000
- Top severity paid
- Critical
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €2,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 | Relative size | Reward |
|---|---|---|
| Critical |
|
€2,000 from €1,250 |
| High |
|
€400 |
| Medium |
|
€100 |
Scope
6 assets you may test, 1 excluded.
Web 4
- hubacc.vznkul.be/services/acceptance/interhub/InterHubService
- hubacc.vznkul.be/services/acceptance/intrahub/IntraHubService
- hub.vznkul.be/services/interhub/InterHubService
- hub.vznkul.be/services/intrahub/IntraHubService
Wildcard domains 2
- hubacc.vznkul.be/*
- hub.vznkul.be/*
Out of scope (1)
- www.vznkul.be
Rules
What the policy asks of you, and the bug types it won't reward, quoted from eHealth Hub VZN KUL (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
If in doubt, please contact us before proceeding to test further systems.
-
Any area that is not explicitly listed in the section above is out of scope.
-
XSS (no self-xss and only on latest versions of browsers)
-
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
Not accepted
-
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
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 21 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.
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
Public CVEs
Published vulnerabilities in this vendor's products, from the 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
The national project “eHealth Hubs & MetaHub” coordinated by the eHealth platform is meant to make medical results from hospitals (and in the near future medical laboratories) available to any caregiver who currently is treating the patient . For detailed information see https://www.ehealth.fgov.be/nl/zorgverleners/online-diensten/hubs-metahub and the URL in the next paragraph. This system supplements the traditional system of addressed ‘email type’ communication to individual referrers.
Before medical data about a patient can be shared, that patient has to grant the ‘eHealth informed consent’ (see http://www.patientconsent.be ).
Further, care providers declare a therapeutic relationship with the patient.
Communication between the hubs and between external physicians and a hub is according to the KMEHR standard: https://www.ehealth.fgov.be/standards/kmehr/content/page/web-services
The scope of this project is confined to the hub exploited by VZNKUL (Vlaams Ziekenhuis Netwerk KU Leuven) implementation of this hub system. The central metahub hub from the Belgian government, the other hubs, and the systems at other partners of this project are out of scope.
Rules of engagement
The Domains listed in the project description are purely informational, and are not in scope.
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 link to OTHER hubs or the central meta-hub are out of scope! The Belgian government and the eHealth platform do not participate in this project. If in doubt, please contact us before proceeding to test further systems.
www.vznkul.be is 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
Bounties
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
Critical
- Access to random patient record
- circumvention of access rules at the Intra-hub (see FAQ)
High
- Service disruption (e.g. config change)
Medium
- Compomise of one user, with user interaction required (Reflective XSS)
FAQ
How does this work? There are 2 separate services to the HUB:
-
Intra-Hub located at https://hub.vznkul.be/services/intrahub/IntraHubService Used by other hospitals/general physisians/etc. To access a patient record, some criteria have to be met:
- Patient needs to have given his/her conformed insent
- Patient needs to have a therapeutic relationship with the requester of the Record
- Patient can exclude specific physicians from his/her Patient Record, Physician cannot be on this "blocklist"
-
Inter-hub located at https://hub.vznkul.be/services/interhub/InterHubService Used by other HUBs. Once granted access, no other checking on specific record is performed. It is the task of the HUB partner to check if the original requester is permitted to access.
Where can I get credentials to login? At this time, we cannot provide a valid certificate to login yet. Use your creativity to find exploits.