Sqills provides the leading inventory, reservation, and ticketing system for the bus and rail industry – S3 Passenger. At Sqills we are on a constant journey of innovation, discovery and global market leadership. Our corporate website provides general information about Sqills.


Responsible disclosure



No Bounty
In scope

Sqills is pleased to announce our responsible disclosure program! We've done our best to resolve most of our known issues and now would like to request your help to find the ones we may have missed! We are specifically looking for:

  • vulnerabilties that lead to modification of content on the corporate website
  • vulnerabilities that provide access to the management system or server that hosts the corporate website
  • vulnerabilities found on management systems that are hosted on * These systems (e.g. Jenkins, Nexus) should not be publicly available.
  • applications hosted on * that are part of another (invite-only) program that has bounties enabled. A finding on this domain may be reported through this program as well. When a report meets the requirements, we will invite you to the bounty program and a bounty will be awarded.

We plan to review our scope each month so make sure to visit regularly or subscribe to our program to receive updates when we make them!

Out of scope

Out of scope domains


  • 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 on pages with no sensitive actions
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing / Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file


  • If a reported vulnerability was already known to us because of our own testing, 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, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities limited to non-current browsers (more than 3 versions removed from what is current) will not be accepted
  • Attacks that require physical access to a victim’s computer/device, man-in-the-middle attack or compromised user accounts
  • Recently disclosed zero-day 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.
  • Reports that state that software is out of date/vulnerable without a proof-of-concept
Rules of engagement

Our promise to you

  • We are happy to respond to any questions, please use the button in the right top corner to contact us
  • 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 or any other service)
  • 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 spend our time in thanking researchers rather than blocking their IP's 😉)

Safe harbour for researchers

Sqills considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. Sqills will not pursue civil action or initiate a complaint for accidental, good faith violations, nor will they file a complaint for circumventing technological measures used by us to protect the scope as part of your ethical hacking activities.

If legal action is initiated by a third party against you and you have complied with the Terms, Sqills will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment


  • RCE (Remote Code Execution)


  • SQL injection


  • Stored XSS without user interaction
  • Privilege escalation
  • Authentication bypass on critical infrastructure


  • XSS which require user interaction


  • Open redirect

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Program specifics
ID check required
Reputation points
last contributors
Overall stats
submissions received
average payout
accepted submissions
total payouts
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
< 2 days
avg. time to triage
< 2 days
closed a submission
created a submission
closed a submission
created a submission
changed the rules of engagement
changed the out of scope
changed the in scope
closed a submission
created a submission
closed a submission