VRT
By VRT (Flemish Radio and Television Broadcasting Organization) Bug bounty on Intigriti vrt.be
- Top reward
- €2,000
- Top severity paid
- Critical
- Assets in scope
- 10
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €2,000
- for critical bugs, from €100.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€2,000 from €1,300 |
| High |
|
€750 |
| Medium |
|
€300 |
| Low |
|
€100 |
- Safe harbor
-
Partial
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
10 assets you may test, 3 excluded.
Web 6
- player.vrt.be
- profiel.vrt.be
- sporza.be
- vrt.be/interactie/121-chat
- vrt.be/vrtmax
- vrt.be/vrtnws
Products and areas 4
- API's
- Brand Sites
- Mobile Applications
- Sockets
Out of scope (3)
- cds.vrt.radio
- innovatie.vrt.be
- shop.*.be
Rules
What the policy asks of you, and the bug types it won't reward, quoted from VRT (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?
-
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.
-
Don't use the following methods as these are our production environments:
-
Bruteforce username/password logins
Not accepted
-
API key disclosure without proven business impact
-
Wordpress usernames disclosure
-
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
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 16 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.
-
Scope removed
Brand Sites
-
Scope removed
vrt.be/interactie/121-chat/
-
Scope removed
Sockets
-
Scope removed
sporza.be
-
Scope removed
profiel.vrt.be
-
Scope removed
cds.vrt.radio (out of scope)
-
Scope removed
vrt.be/vrtnws
-
Scope removed
player.vrt.be
-
Scope removed
vrt.be/vrtmax
-
Scope removed
innovatie.vrt.be (out of scope)
-
Scope removed
shop.*.be (out of scope)
-
Scope removed
Mobile Applications
-
Scope removed
API's
-
Scope added
https://www.vrt.be/interactie/121-chat/
-
Scope added
be.vrt.ketnet.ketnetjr
-
Scope added
4ever.ketnet.be
-
Scope added
1001982587
-
Scope added
stubru.be/luister/select
-
Scope added
api.vrt.radio
-
Scope added
sport-components.sporza.be
-
Scope added
api.sporza.be
-
Scope added
vrt.be/vrtnu
-
Scope added
remix-cf.lwc.vrtcdn.be
-
Scope added
remix-cf-vrt.akamaized.net
-
Scope added
ondemand-vrt.akamaized.net
-
Scope added
1337574835
-
Scope added
media-services-public.vrt.be
-
Scope added
login.vrt.be
-
Scope added
live-cf.lwc.vrtcdn.be
-
Scope added
live-cf-vrt.akamaized.net
-
Scope added
ondemand-cf.lwc.vrtcdn.be
-
Scope added
vrtnws-api.vrt.be
-
Scope added
Corporate Sites
-
Scope added
be.vrt.vrtnu
-
Scope added
www.ketnet.be
-
Scope added
senior-bff.ketnet.be
-
Scope added
privacy.ketnet.be
-
Scope added
magazine.ketnet.be
-
Scope added
kaatje.ketnet.be
-
Scope added
juniormusical.ketnet.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
Flemish Radio and Television Broadcasting Organization bugbounty program
Rules of engagement
Our promise to you
- We will respond to report as soon as possible!
- 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 😉)
- Don't use the following methods as these are our production environments:
- Bruteforce username/password logins
In scope
The VRT (Flemish Radio and Television Broadcasting Organization) considers it important that its information and systems are secure. If you have found a vulnerability in one of the items in scope, please let us know so that we can take measures as quickly as possible. We would like to work with you to protect our audience and our systems in a better way.
Out of scope
Domains
- All VRT domains not explicitily mentioned in the in scope domains, unless they are used in the natural flow for using the products.
- gigya.com owned parts of the flow
- qualtrics.com owned parts of the flow
- shop.*.be
- innovatie.vrt.be
- Salesforce owned parts of the flow: https://www.vrt.be/heb-je-een-vraag/*
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
- Data visibility within a shared family account (between child profiles or between child and parent profiles)
- CORS wildcard origin (*) in use on client-facing API endpoints
- Missing input validation on client-facing API endpoints
- No rate limiting on client-facing REST API endpoints
- Error messages on client-facing endpoints may expose internal implementation details
- Chat: JWT tokens are not cryptographically verified server-side
- Chat: Access tokens transmitted in request body instead of Authorization header
- Chat: No API Gateway authorizer on client-facing chat endpoints
- Chat: WebSocket connections accepted without authentication prior to the authentication message
- Chat: Child account restrictions not consistently enforced across all client-facing endpoints
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
- The use of 3rd party malicious apps for stealing credentials
- The use of large GraphQL query attacks
- UI or UX inconsistencies, including parental control descriptions that do not fully reflect functional behavior, are not considered security vulnerabilities unless they result in a verifiable bypass of a technical security mechanism.
Mobile
- Shared links leaked through the system clipboard
- Any URIs leaked because a malicious app has permission to view URIs opened
- The absence of certificate pinning
- Sensitive data in URLs/request bodies when protected by TLS
- Lack of obfuscation
- Path disclosure in the binary
- Lack of jailbreak & root detection
- Crashes due to malformed URL Schemes
- Lack of binary protection (anti-debugging) controls, mobile SSL pinning
- Snapshot/Pasteboard leakage
- Runtime hacking exploits (exploits only possible in a jailbroken environment)
- The use of 3rd party malicious apps for stealing credentials
- In the VRT MAX iOS app, after logging out users have access to the chat of the previously logged in user.
TEMPORARY OUT OF SCOPE:
- CPDoS attacks on all VRT related products
- Known authentication and secrets management weaknesses in the messaging and chat APIs are currently being remediated
Severity
This program follows Intigriti's triage standards
FAQ
Can I create a test account?
Yes and you are encouraged to do so! Please use your @intigriti.me email address for the account creation. More info can be found here: https://kb.intigriti.com/en/articles/2642598-intigriti-me-email-alias