Program Overview
UZ Leuven runs a bug bounty program on Intigriti with a maximum payout of $5,000. The program has 34 in-scope assets.
34
In-Scope Assets
$5,000
Max Payout
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| autodiscover.uzleuven.be | URL | ||
| ecrf.uzleuven.be | URL | ||
| extranet-asa.uzleuven.be | URL | ||
| extranet.uzleuven.be | URL | ||
| liquidfiles.uzleuven.be | URL | ||
| mx1.uzleuven.be | URL | ||
| mx2.uzleuven.be | URL | ||
| pcrstudioruzb.uzleuven.be | URL | ||
| prddsplunkhf.uzleuven.be | URL | ||
| sts.uzleuven.be | URL | ||
| www.uzleuven.be | URL | ||
| 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 | IPRANGE | ||
| wp5-truststroke.uzleuven.be | URL | ||
| cardsonline.azdiest.be | URL | ||
| liquidfilestest.uzleuven.be | URL | ||
| random.uzleuven.be/random/ | URL | ||
| teststs.uzleuven.be | URL | ||
| w1.uzleuven.be | URL | ||
| cardsonlinetst.azdiest.be | URL | ||
| *.kwsdose.be | WILDCARD | ||
| *.playuzleuven.be | WILDCARD | ||
| *.uzleuven.* | WILDCARD | ||
| *.contactallerg(y|ie).uzleuven.be | WILDCARD | ||
| *.mir.uzleuven.be | WILDCARD | ||
| *dev.uzleuven.be | WILDCARD | ||
| *idp*.uzleuven.be | WILDCARD | ||
| *stag*.uzleuven.be | WILDCARD | ||
| files.uzleuven.be | URL | ||
| kumulus.uzleuven.be | URL | ||
| mijnacc.uzleuven.be | URL | ||
| mirc.uzleuven.be | URL | ||
| prddnighting01.uzleuven.be | URL | ||
| w1.uzleuven.be/random | URL | ||
| ziekenhuisschool.be | URL |
Out-of-Scope Assets
- boekentoy.uzleuven.be
- uz-laboboeken.web.app
- laboboeken.uzleuven.be
- boekentoy.firebaseio.com
- uz-laboboeken.firebaseio.com
- jobs.uzleuven.be
- uzleuven.atlassian.net
- vacatures.uzleuven.be
Tips for Hacking UZ Leuven
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking UZ Leuven?
Sign up on Intigriti, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does UZ Leuven pay bounties?
Yes, UZ Leuven offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does UZ Leuven accept?
UZ Leuven accepts reports for vulnerabilities found in their 34 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.