- Top reward
- €5,000
- Top severity paid
- Critical
- Assets in scope
- 34
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €5,000
- for critical bugs, from €50.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Intigriti lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€5,000 from €850 |
| High |
|
€1,500 from €300 |
| Medium |
|
€500 from €125 |
| Low |
|
€100 from €50 |
- Safe harbor
-
Full
We respect the safe harbour clause that you can find below
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
34 assets you may test, 8 excluded.
Web 25
- autodiscover.uzleuven.be
- cardsonline.azdiest.be
- cardsonlinetst.azdiest.be
- ecrf.uzleuven.be
- extranet-asa.uzleuven.be
- extranet.uzleuven.be
- files.uzleuven.be
- kumulus.uzleuven.be
- liquidfilestest.uzleuven.be
- liquidfiles.uzleuven.be
- mijnacc.uzleuven.be
- mirc.uzleuven.be
- mx1.uzleuven.be
- mx2.uzleuven.be
- pcrstudioruzb.uzleuven.be
- prddnighting01.uzleuven.be
- prddsplunkhf.uzleuven.be
- random.uzleuven.be/random
- sts.uzleuven.be
- teststs.uzleuven.be
- w1.uzleuven.be
- w1.uzleuven.be/random
- wp5-truststroke.uzleuven.be
- www.uzleuven.be
- ziekenhuisschool.be
Wildcard domains 8
- *.contactallerg(y|ie).uzleuven.be
- *dev.uzleuven.be
- *idp*.uzleuven.be
- *.kwsdose.be
- *.mir.uzleuven.be
- *.playuzleuven.be
- *stag*.uzleuven.be
- *.uzleuven.*
Networks 1
- 193.58.149.121,193.58.149.98,193.58.149.82,193.58.149.101,193.58.149.107,193.58.149.108,193.58.149.111
Out of scope (8)
- boekentoy.firebaseio.com
- boekentoy.uzleuven.be
- jobs.uzleuven.be
- laboboeken.uzleuven.be
- uz-laboboeken.firebaseio.com
- uz-laboboeken.web.app
- uzleuven.atlassian.net
- vacatures.uzleuven.be
Rules
What the policy asks of you, and the bug types it won't reward, quoted from UZ Leuven (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Provide detailed but to-the point reproduction steps
-
Include a clear attack scenario. How will this affect us exactly?
-
Remember: quality over quantity!
-
Please do *not* discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
-
Please do *not* use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners.
-
Please DO NOT use any scanner or tool on contact forms.
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, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 10 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
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Scope removed
mx1.uzleuven.be
-
Scope removed
*.kwsdose.be
-
Scope removed
prddsplunkhf.uzleuven.be
-
Scope removed
jobs.uzleuven.be (out of scope)
-
Scope removed
mijnacc.uzleuven.be
-
Scope removed
prddnighting01.uzleuven.be
-
Scope removed
random.uzleuven.be/random/
-
Scope removed
extranet-asa.uzleuven.be
-
Scope removed
uzleuven.atlassian.net (out of scope)
-
Scope removed
www.uzleuven.be
-
Scope removed
*stag*.uzleuven.be
-
Scope removed
*dev.uzleuven.be
-
Scope removed
wp5-truststroke.uzleuven.be
-
Scope removed
*.playuzleuven.be
-
Scope removed
boekentoy.firebaseio.com (out of scope)
-
Scope removed
193.58.149.121,193.58.149.98,193.58.149.82,193.58.149.101,193.58.149.107,193.58.149.108,193.58.149.111
-
Scope removed
*.uzleuven.*
-
Scope removed
sts.uzleuven.be
-
Scope removed
w1.uzleuven.be/random
-
Scope removed
uz-laboboeken.firebaseio.com (out of scope)
-
Scope removed
liquidfilestest.uzleuven.be
-
Scope removed
*.contactallerg(y|ie).uzleuven.be
-
Scope removed
ecrf.uzleuven.be
-
Scope removed
kumulus.uzleuven.be
-
Scope removed
*.mir.uzleuven.be
-
Scope removed
w1.uzleuven.be
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
UZ Leuven is a university hospital where patients can count on specialised care and innovative treatments, combined with humane attention and respect for every person. Every day, almost 10,000 passionate employees provide the best possible custom-made care. Future care providers and employees receive high-quality training in UZ Leuven, with a view lifelong learning and innovation. As a pioneer in clinical research, the hospital also contributes to future patient care.
Rules of engagement
Our promise to you
- We are happy to respond to any questions, please use the button in the right top corner for this.
- We respect the safe harbour clause that you can find below
Your promise to us
- Provide detailed but to-the point reproduction steps
- Include a clear attack scenario. How will this affect us exactly?
- Remember: quality over quantity!
- Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
- Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)
In scope
We are happy to announce our bug bounty program! We've done our best to clean most of our known issues and now would like to request your help to spot the once we missed! We are specifically looking for:
- leaking of personal and medical data
- administrative access
- ...
Please DO NOT use any scanner or tool on contact forms.
Out of scope
Domains
- jobs.uzleuven.be
- vacatures.uzleuven.be
- uzleuven.atlassian.net
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
- Broken links, unless you can prove to us this has a larger impact to us.
General
- Declarations of interest (DOI) are out of scope because we are expected to publish these files on the internet for anyone to read. Using a google dork to find them is not regarded as a valid finding.
- 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, including non-volumetric denial of service attacks, unless you can prove significant impact (e.g. impacting urgent healthcare).
- 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
This program follows Intigriti's triage standards
Cool-down period for zero-days
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. We may decide to award a bonus.
FAQ
Where can we get credentials?
We currently don’t offer any credentials.