- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- No safe harbor
- No promise about legal action.
- Replies within 5 days
- As the policy promises.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 5 days
It may take up to five business days for us to analyze and find a report of sufficient quality.
- Hall of fame
-
Yes
We want to thank everybody who reported a vulnerability in a responsible way in our Hall of Fame.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 2 excluded.
Domains 1
- utwente.nl
Out of scope (2)
- student.utwente.nl
- www.utwente.nl/en/cyber-
Rules
What the policy asks of you, and the bug types it won't reward, quoted from University of Twente's policy.
While testing
-
Reports must be clear and contain the steps necessary to reproduce the vulnerability.
-
The steps need to be in the body of the message.
-
Reports with the details in a PDF, DOC(x), or other attachments are unacceptable and will be discarded!
-
It makes no sense to inquire about progress earlier.
Not accepted
-
No authentication (anonymous access) for public FTP servers, especially mirrors for open-source projects.
-
Disclosure of publicly available software or source code.
-
HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
-
Fingerprint and other ways to detect versions that are disclosed on common/public services.
-
Missing limits on login attempts.
-
Clickjacking and issues that are only exploitable through clickjacking.
-
Lack of Secure/HTTP-Only flags on non-sensitive Cookies.
-
OPTIONS HTTP method enabled.
-
anything related to HTTP security headers
-
SSL forward secrecy not enabled.
-
weak/insecure cipher suites.
-
Lack of SPF, DKIM, DMARC or BIMI records or any other issues involving these protocols.
-
Host header injection.
-
Reporting older versions of any software without proof of concept or working exploit.
-
Information leakage in metadata.
-
Systems and protocols that can be used in DDoS attacks.
-
trivial vulnerabilities or bugs that cannot be abused
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
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.