- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report through their form
- tidio.com/security.txt
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 2 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
we will make our best effort to reward you.
- Response
-
Within 2 days
Time to get a first reply: 2 working days
- Safe harbor
-
Partial
We won’t report you to authorities for acting in good faith that will help to prepare Proof-of-Concept (view PoC Guidelines )
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test.
APIs 1
- https://api-v2.tidio.co
Web 1
- https://tidio.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Tidio's policy. "We" in these lines means the program, not this site.
While testing
-
Using automated vulnerability scanners (turbo-intruder, fuzzes, etc.), which generate high traffic and put a high load on our infrastructure
-
Sociotechnical attacks (phishing, spear-phishing, etc.) on Tidio employees
-
Data Exfiltration
-
Performing actions that have negative consequences on our service – mass SPAM attack, brute-force or DoS attacks, etc
-
Releasing information about vulnerabilities to people not connected to Tidio company
-
Using private or sensitive data of our clients for testing purposes
-
Testing the vulnerabilities on accounts that you do not own
-
DO NOT escalate any spotted vulnerability while crafting PoC or testing.
Not accepted
-
Email Spoofing – incorrect SPF/DKIM/DMARC configuration
-
Clickjacking: X-Frame-Options
-
DoS Attacks
-
Lack of a security flag – HttpOnly, Secure
-
Lack of security headers – without showing a potential influence on the security
-
Brute-force attacks
-
Self-XSS – running JavaScript code in your project
-
HTML Injection – injecting HTML code into contact forms etc
-
CSV Injection
-
Using weak SSL ciphers
-
Lack of CAPTCHA
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 6 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.