The online enrollments application allows students to apply for educational programs at the university or at university colleges. Every year approximately 40.000 applicants enter their personal information and educational preferences into this application. We challenge you to find the bugs in our online enrollment application.

0.1 - 3.9
4.0 - 6.9
7.0 - 8.9
9.0 - 9.4
9.5 - 10.0
Tier 2
Tier 2
Up to €2,000
Rules of engagement
Not applicable
max. 5 requests/sec
Not applicable

Types of users

  • Only logged in users can access the Enrollment application. The login is provided by the Identity & Access Management system of KU Leuven.


  • Write your report in Dutch or English.
  • Describe the problem in sufficient detail and include the necessary evidence, such as IP addresses, log entries, screenshots, etc.
  • Provide detailed but to-the-point reproduction steps
  • Include a clear attack scenario; a step by step guide in the PoC is highly appreciated
  • Remember: quality over quantity
  • Only notify the ICTS department of KU Leuven of your findings, and only via this procedure. Do not publish details about the security issue through other channels. Making the problem known through other channels or the media, even before or after notifying the KU Leuven via this procedure and even when not all details are provided, will be considered irresponsible behaviour and can still lead to the filing of criminal charges.
  • Do not exploit the identified leak: only collect the information necessary to demonstrate its existence.
    Handle any found data in a responsible manner: if you can demonstrate that there is a security problem with a small portion, do not go any further
    Please do NOT discuss bugs before they are fixed

Our promise

  • We will response to your report as soon as possible, if you have provided contact information.
  • If we require additional information, we may choose to contact you, if possible.
  • We will do everything possible to solve any shortcomings as quickly as possible, and we will keep you posted.
Tier 2

🇬🇧🇳🇱 the registration/login part on itself is out of scope for the program

Tier 2


In scope

The scope of this project is the online enrollment application:

The above link is used to login or create an account. Keep in mind that the registration and login process are considered as out-of-scope. Once logged in, you will proceed to the actual enrollment application. From there, it is in scope.

We are particularly interested in, but not limited to, ways to exploit the tool using:

  • Horizontal or vertical privilege escalation
  • Exploits that facilitate information theft
  • Exploits that facilitate data modification


Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

Out of scope


In order to enroll users must first create an account to enter the application here:

The registration/login part on itself is out of scope for the program.


  • 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


  • 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 assessment

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 KU Leuven on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.


  • Remote code execution
  • Access to the underlying infrastructure


  • Acquire sensitive data of our users
  • Full database access
  • Vertical privilege escalation
  • Access to all user data or access to a targeted user
  • Data loss


  • Access to data of random users
  • Stored cross-site scripting
  • Impersonation of other user (1 user per time)


  • Reflected cross-site scripting with low or no user interaction
  • Stored cross-site scripting that requires a lot of user interaction

How should we create the accounts?

In order to enroll users must first create an account to enter the application here:

When creating an account, you have to provide first name and last name. First name must be "intigriti" and last name must be "Test". Mailaddress must be your intigriti-mailaddress.

How long does it take to fix a vulnerability?

Our goal is to implement a fix as soon as possible. Depending on the criticality and the affected system it can take up to multiple months to implement a fix.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid Intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

last contributors
Last 90 day response times
avg. time first response
< 2 days
avg. time to decide
+3 weeks
avg. time to triage
< 4 days
KU Leuven
closed a submission
created a submission
KU Leuven
accepted a submission
KU Leuven
accepted a submission
created a submission
KU Leuven
changed the bounties
KU Leuven
changed the in scope
created a submission
KU Leuven
changed the out of scope
KU Leuven
closed a submission