Skip to content

Tiqets

Vulnerability disclosure program on Self-hosted tiqets.com

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

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No While we do not offer a bounty program, we highly value the contributions of the security community in identifying these issues to help keep our systems and applications secure.
Safe harbor
Full If you follow the instructions below, we will not take any legal action against you regarding your report.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 2 excluded.

Wildcard domains 2

  • externally accessible systems and services under the tiqets.com domain, including subdomains
  • *.tiqets.com

Domains 1

  • tiqets.com
Out of scope (2)
  • Any service that results in interaction with our customer support agents.
  • Other third party SAAS services that are used by Tiqets.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Tiqets's policy. "We" in these lines means the program, not this site.

While testing

  • Do not disclose the problem to others until it has been resolved.
  • Do not exploit the vulnerability by unnecessarily copying, deleting, adapting, or viewing data, or by downloading more data than needed to demonstrate the vulnerability.
  • Do not generate many unpaid orders.
  • Do not generate a flood of errors in our monitoring by excessively using automated scanning tools.
  • Do do not contact our customer support agents or any other Tiqets employee other than the security team through [email protected].
  • If you manage to book a ticket for free, do not book any additional tickets.
  • If you bypass our security systems, do not make any changes.
  • Erase all data obtained through the vulnerability once it is reported to our security team.

Not accepted

  • Automated scan reports
  • Open HTTP redirections
  • Missing HTTP security headers and cookie flags on insensitive cookies
  • Rate-limit deficiencies or brute-force attacks
  • DoS or DDoS attacks
  • Social engineering, Phishing or spam attacks (including SPF/DKIM/DMARC-related issues)
  • Vulnerabilities found in third-party services
  • Issues requiring direct physical access to the victim’s machine or device
  • Placing malware (virus, worm, Trojan horse, etc.).
  • Use of automated scanners without requesting explicit permission.

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.