- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- 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.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
Scope
6 assets you may test, 3 excluded.
Wildcard domains 6
- *.kiwa.com
- *.kiwaimpact.com
- *.kiwa.info
- *.kiwa.nl
- *.kiwa.no
- *.kiwa.se
Out of scope (3)
- https://careers.kiwa.com
- https://qr.kiwa.com
- https://www.kiwa.com/en/contact
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Kiwa Vulnerability Disclosure Program (via Intigriti)'s policy. "We" in these lines means the program, not this site.
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)
-
We ask you not to abuse a vulnerability, but to report the issue to us so that we can take the necessary measures.
-
Please report the vulnerability before you announce the 'leak' to the outside world, so we can solve it as quickly as possible.
-
Our Vulnerability Disclosure Program is however not an invitation to actively scan our business network to discover weak points.
-
you can attempt to self-register on the applications but please don't forget to use your @intigriti.me address.
Not accepted
-
API key disclosure without proven business impact
-
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
Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 17 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.
-
Reward raised
Maximum no amount → no amount
-
Status
Program status changed
-
Status
Program status changed
-
Scope removed
https://careers.kiwa.com/ (out of scope)
-
Scope removed
*.kiwa.info
-
Scope removed
https://www.kiwa.com/en/contact/ (out of scope)
-
Scope removed
*.kiwa.se
-
Scope removed
https://qr.kiwa.com/ (out of scope)
-
Scope removed
*.kiwa.com
-
Scope removed
*.kiwa.nl
-
Scope removed
*.kiwaimpact.com
-
Scope removed
*.kiwa.no
-
Scope added
*.kiwa.fi
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
Kiwa is an autonomous global organization in Testing, Inspection and Certification (TIC), training and consultancy services. We create trust by contributing to the transparency of the quality, safety and sustainability of your organization’s products, services, processes, systems and employees, as well as personal and environmental performance. You have the ambition and we help you to go forward!
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)
In scope
Introduction
We are happy to announce our Vulnerability Disclosure Program! At Kiwa, we consider the security of our ICT systems and our websites of utmost importance, and we therefore strive for the highest possible level of security. Despite the great care we take with respect to ICT security, weaknesses can still remain. We ask you not to abuse a vulnerability, but to report the issue to us so that we can take the necessary measures.
Have you found a vulnerability in our websites or in one of our other (online) systems? Then please report your findings to us as soon as possible through this portal. Please report the vulnerability before you announce the 'leak' to the outside world, so we can solve it as quickly as possible.
We would like to work together with you to better protect our systems and to remediate a vulnerability as soon as possible. Our Vulnerability Disclosure Program is however not an invitation to actively scan our business network to discover weak points.
Feedback 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
Domains
- Any root domain that is not listed in the Domains section, is out of scope for this program
- https://careers.kiwa.com/
- https://www.kiwa.com/en/contact/
- https://qr.kiwa.com/
Application
- API key disclosure without proven business impact
- 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
How do I report vulnerabilities to Kiwa?
Register an account at the Intigriti bug bounty hunting platform here and start reporting vulnerabilities, earning reputation points and possibly more!
Where can I get credentials for the applications?
We currently don’t offer any credentials to researchers. However, you can attempt to self-register on the applications but please don’t forget to use your @intigriti.me address.