Skip to content

Dutch Lottery VDP

By Nederlandse Loterij Vulnerability disclosure program on Intigriti nederlandseloterij.nl

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
9
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 2 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What Intigriti lists as the payout for each severity.

This program does not pay cash rewards.

Response
Within 2 days We aim to validate all submissions within the below timelines, once your submission has been verified by Intigriti.

Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

9 assets you may test.

Web 8

  • www.eurojackpot.nederlandseloterij.nl
  • www.krasloten.nederlandseloterij.nl
  • www.lotto.nederlandseloterij.nl
  • www.luckyday.nederlandseloterij.nl
  • www.miljoenenspel.nederlandseloterij.nl
  • www.nederlandseloterij.nl
  • www.staatsloterij.nederlandseloterij.nl
  • www.toto.nl

Products and areas 1

  • See the CSV file attached in the In-scope section for a full list of assets in scope

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Dutch Lottery VDP (via Intigriti)'s policy.

While testing

  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Not accepted

  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't 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

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 33 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.

  1. Scope removed

    www.luckyday.nederlandseloterij.nl

  2. Scope removed

    www.staatsloterij.nederlandseloterij.nl

  3. Scope removed

    www.krasloten.nederlandseloterij.nl

  4. Scope removed

    www.nederlandseloterij.nl

  5. Scope removed

    www.miljoenenspel.nederlandseloterij.nl

  6. Scope removed

    www.toto.nl

  7. Scope removed

    See the CSV file attached in the In-scope section for a full list of assets in scope

  8. Scope removed

    www.lotto.nederlandseloterij.nl

  9. Scope removed

    www.eurojackpot.nederlandseloterij.nl

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search 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

At Nederlandse Loterij, we consider the security of our systems to be of paramount importance. Despite our efforts to secure our systems, it is possible that a vulnerability or weakness may still occur. If you discover a vulnerability or weakness in one of our systems or the associated or underlying domains and/or specific domains of third parties and/or partners, we would appreciate it if you would inform us so that we can take measures as soon as possible.

Rules of engagement

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation times

We aim to validate all submissions within the below timelines, once your submission has been verified by Intigriti.

Vulnerability Severity Time to validate
Exceptional 2 Working days
Critical 2 Working days
High 5 Working days
Medium 15 Working days
Low 15 Working days

In scope

Introduction

We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!

Our worst-case scenarios are: (Examples below)

  • A malicious actor manipulates lottery systems, draw logic, ticket validation, or prize allocation processes, potentially undermining the fairness and integrity of the lottery.
  • Sensitive customer data is exposed, including identity details, payment information, account history, or documents used for age and identity verification.
  • Player accounts are compromised, allowing attackers to access balances, claim winnings, change payout details, or abuse stored payment methods.
  • The platform is abused for fraud, money laundering, bonus abuse, or automated bot activity, creating regulatory, financial, and reputational risk for the lottery provider.
  • Full list of all in scope assets attached below

Out of scope

Application

  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't 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 aren't 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

This program follows Intigriti's triage standards based on the proof of concept.

FAQ

Where can we get credentials for the websites?

You can self-register on the application but please don’t forget to use your @intigriti.me address. (Please note that self regristration is limited to Dutch residents and citizens)