- Top reward
- €13,337
- Top severity paid
- Critical
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €13,337
- for critical bugs.
- 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 |
|
€13,337 from €500 |
| High |
|
€6,000 from €250 |
| Medium |
|
€3,000 from €200 |
| Low |
|
€500 from €50 |
Scope
5 assets you may test, 16 excluded.
Wildcard domains 3
- *.intigriti.me
- *.pwn.intigriti.rocks
- vpn.intigriti.rocks/*
Web 2
- https://metabase.pwn.intigriti.rocks
- www.intigriti.com
Out of scope (16)
- any intigriti CTF or challenge
- our hubspot pages (/hs-fs/, /hubfs/, /hs/, /_hcms/, landing/, report/, webinar/, /datasheet, /customer/, /video/...)
- autodiscover.intigriti.com
- careers.intigriti.com
- click.intigriti.com
- go.intigriti.com
- kb.intigriti.com
- mail.intigriti.com
- newsletter.intigriti.com
- posthog.intigriti.com
- status.intigriti.com
- swag.intigriti.com
- trust.intigriti.com
- *.intercom.io
- *.intigriti.io
- *.intigriti.net
Rules
What the policy asks of you, and the bug types it won't reward, quoted from intigriti (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)
-
Be aware that client isolation is turned off on our VPN to facilitate mobile testing, as always run an endpoint firewall.
Not accepted
-
Prompt injection without proven business impact (e.g. extracting content from another submission)
-
API key disclosure without proven business impact
-
Wordpress usernames disclosure
-
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 9 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
trust.intigriti.com (out of scope)
-
Scope removed
*.intigriti.me
-
Scope removed
kb.intigriti.com (out of scope)
-
Scope removed
autodiscover.intigriti.com (out of scope)
-
Scope removed
*.intercom.io (out of scope)
-
Scope removed
mail.intigriti.com (out of scope)
-
Scope removed
any intigriti CTF or challenge (out of scope)
-
Scope removed
status.intigriti.com (out of scope)
-
Scope removed
our hubspot pages (/hs-fs/, /hubfs/, /hs/, /_hcms/, landing/, report/, webinar/, /datasheet, /customer/, /video/...) (out of scope)
-
Scope removed
careers.intigriti.com (out of scope)
-
Scope removed
*.intigriti.io (out of scope)
-
Scope removed
go.intigriti.com (out of scope)
-
Scope removed
swag.intigriti.com (out of scope)
-
Scope removed
www.intigriti.com
-
Scope removed
*.pwn.intigriti.rocks
-
Scope removed
newsletter.intigriti.com (out of scope)
-
Scope removed
posthog.intigriti.com (out of scope)
-
Scope removed
click.intigriti.com (out of scope)
-
Scope removed
*.intigriti.net (out of scope)
-
Scope removed
https://metabase.pwn.intigriti.rocks/
-
Scope removed
https://vpn.intigriti.rocks/*
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
At intigriti, we practice what we preach. We’ve built the platform with the greatest care and attention for security, but all software contains bugs and we are no exception to this rule. We encourage you to responsibly disclose any security vulnerabilities you may encounter and we will reward you accordingly.
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 will validate all submissions within the below timelines, once your submission has been verified by intigriti. Submissions validated outside of this may be awarded a €25 bonus.
| 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 |
This remains at the discretion of intigriti to award.
Check our fix We offer up to €50 bonus to verify a resolved issue for us (when requested). This remains at the discretion of intigriti to award.
In scope
Introduction
We are happy to announce a brand new look for our program! We've made a lot of changes to the platform over the years and you have been there alongside to help us. All the tests will now be performed on our test (PWN) environment, which will allow you to play around without any restrictions.
Our worst-case scenarios are:
- access to submission data from unauthorised users - submissions are our most prized and security sensitive asset
- disclosure of PII from any of our platform's users
- vertical and horizontal privilege escalation
Out of scope
General
- In case that a reported vulnerability was already known to us from our 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, take a look at our Zero Day program
- Reports that state that software is out of date/vulnerable without a proof-of-concept
- Be aware that client isolation is turned off on our VPN to facilitate mobile testing, as always run an endpoint firewall.
Application
- Prompt injection without proven business impact (e.g. extracting content from another submission)
- API key disclosure without proven business impact
- Wordpress usernames disclosure
- 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.
- This also includes: Bypassing submission create rate-limits via race conditions.
- 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
Infrastructure
- Open ports without an accompanying proof-of-concept demonstrating a vulnerability
- Recently disclosed 0day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
- Weak/expired SSL configurations and SSL/TLS scan reports (this means output from sites such as SSL Labs)
Severity
We use our triage standards, using CVSSv4 as a scoring system and applying a business impact modifier if needed.
You can find more details about it here.
Exceptions to these standards may apply and are listed below:
- Actual subdomain takeovers on out-of-scope assets without any further exploitation will be rewarded with a maximum bounty of €50.
FAQ
How do I access the test environment?
In order to access the PWN environment you have to use our VPN. There are 4 easy steps for that:
- Visit the VPN portal.
- Navigate to your profile and download the peer (VPN config).
- Load this config in your preferred WireGuard client.
- Browse to https://app.pwn.intigriti.rocks. You should be able to access the PWN environment now.
How do I get credentials?
We don't offer credentials, but you can create your own researcher account on the PWN environment at https://login.pwn.intigriti.rocks and start testing. Feel free to create as many accounts you need.
How do I get access to multiple types of programs on the testing environment?
We will make sure that the PWN environment has all the program types that are present on production. We will proactively invite new researcher on private programs, but feel free to reach us at [email protected] for any requests regarding invites and applications.
Why does https://www.pwn.intigriti.rocks not work?
We do not have a version of our public/marketing website for the PWN environment. We have added that as a separate domain in our scope and can be tested at www.intigriti.com.