Toast VDP

Description

Toast is the all-in-one digital technology platform built specifically for the restaurant community. We serve a diverse range of customers—from distinct local cafes to nationwide enterprise chains—powering front-of-house operations, back-of-house management, and guest-facing technology. Our platform combines powerful cloud-based software with durable hardware to help restaurants operate efficiently, delight guests, and thrive in a digital-first world.

What do we do?

We provide a comprehensive operating system for restaurants. The Toast platform unites Point of Sale (POS), Kitchen Display Systems (KDS), Online Ordering, and Team Management into a single, streamlined ecosystem.

Beyond secure payment processing, we handle critical workflows including inventory management, payroll, loyalty programs, and third-party delivery integrations. We help restaurateurs streamline their operations, grow their business, and deliver a seamless dining experience to guests everywhere.

Intention for this program

To partner with the global security research community in identifying and addressing potential vulnerabilities across Toast's hardware, software, and cloud infrastructure.

Security is a priority for the Toast ecosystem given its role in daily restaurant operations. Your responsible disclosure helps us validate our defenses and ensures a reliable, secure experience for the merchants and guests who utilize our services.

The targets listed below are publicly accessible, but we do not provide accounts for accessing authenticated functions. If you can create self-register for any application, feel free to do so using your Intigriti email (intigriti.me). If account creation requires a phone number, please include a reference to Intigriti in your profile, such as using 'intigriti-' in the first name field or something similar.

Bounties

This is a responsible disclosure program without bounties.

Rules of Engagement

• @intigriti.me Required
• User agent: Not applicable
• Automated tooling: max. 5 requests/sec
• Request header: Not applicable

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)

Safe harbour for researchers is applied

Assets

In Scope

Security is at the heart of how we serve our community. We strongly encourage collaboration with security experts to help keep our ecosystem safe. Our disclosure policy ensures that researchers have a clear, protected avenue to flag potential issues so we can address them together.

Out of Scope

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program

Application

• 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

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

Severity Assessment

This program follows Intigriti's triage standards based on the proof of concept.

FAQ

Where can we get credentials for the apps?

You can self-register for some of the applications, but please be sure to use your @intigriti.me address.