Upserve is committed to protecting the privacy and security of our users. We recognize the valuable role security researchers play in making our services more secure and are committed to working with you to verify and resolve legitimate security vulnerabilities. We ask that you carefully review this policy and scope to ensure the best experience for all involved.

Important Notes

Do not test with the live upserve.com site. Please review the scope for details on the test site URL specific for security research

Public Disclosure Policy

Upserve supports public disclosure of most vulnerabilities following resolution. We ask that you not share vulnerability details with anyone other than Upserve or HackerOne prior to approved public disclosure through the HackerOne platform.

• In most cases, Upserve will allow public disclosure of vulnerabilities within 30 days of resolution.

• In some cases, Upserve will request that public disclosure is delayed. (for example, if we need to conduct private notifications first)

• In limited cases, Upserve may request that a report remain private. In these cases, we will maintain open communication with the researcher about why we feel this is important.

• Follow HackerOne's disclosure guidelines.

Program Rules

• Please check the list of out-of-scope vulnerabilities and known issues before submitting a report.

• Do not run automated scans without checking with us first. They are often very noisy and disruptive.

• Social engineering (e.g. phishing, vishing, smishing) is prohibited.

• Make every effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.

• Only interact with accounts you own or with the explicit permission of the account holder.

• If we receive several reports for the same issue, we offer the bounty to the earliest report for which we had enough actionable information to identify the issue.

• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

• Our rewards are based on the impact of a vulnerability and we use CVSS v3 to guide our decisions on vulnerability impact.

• Public Zero-day vulnerabilities that have had an official patch for less than 30 days will be awarded on a case by case basis.

• Zero-day vulnerabilities found on third-party libraries/services used by Upserve will be awarded on a case by case basis. These vulnerabilities should be reported directly to the library or service maintainer.

A Note on Similar Submissions

We ask that researchers who are able to identify the same or similar types of issues in multiple locations across one of our applications combine those findings into a single submission that includes a description as well as the various locations where vulnerabilities have been identified. This greatly assists us in our triage process and allows us to process your submissions faster. The combined submissions will be evaluated holistically and will receive rewards corresponding to the collective findings. For example, if an application is discovered to have broken access control on a number of API endpoints, please submit a single submission that includes a list of those API endpoints. If separate submissions are made, they may be inadvertently closed as duplicates.

Test References and Documentation

Read carefully for instructions and tips on testing:

• Upserve Loyalty (https://app.upserve.com/b/upserve-hacker-cafe/) is a React application with a Ruby on Rails backend. REST API calls are made to app.upserve.com/c/ and cards.swipely.com. The application allows a consumer to register an account and enroll one or more credit cards into a restaurant's loyalty program. Purchases made by the consumer at the restaurant are tracked in the loyalty program and a reward is given when the consumer's account reaches a specified level. It is not currently possible for researchers to generate sales that apply to the loyalty program. We are interested in vulnerabilities that would allow a consumer to fraudulently add points to their own account or steal points from other accounts. Use the provided test restaurant Upserve Hacker Cafe only. Testing on any other restaurant is prohibited without approval from Upserve.

  • To create a customer account, navigate to https://app.upserve.com/b/upserve-hacker-cafe/, enter in your email address, enter in a credit card number (either your own or you can use a credit card generator to create a fake one). The application will reject duplicate card numbers.

  • cards.swipely.com provides an endpoint for adding payment cards to the vault. The endpoint returns a token which should not be reversible. This API should not be able to provide back full payment card numbers.

• Upserve Online Ordering (OLO) (https://app.upserve.com/s/upserve-hacker-cafe) is a React application with a Ruby on Rails backend. REST API calls are made to orders.upserve.com and payments.upserve.com. Orders can be submitted to the test restaurant linked in this plan using any valid credit card number. Credit cards will not be charged or authorized with this restaurant. Testing on any other restaurant is prohibited without approval from Upserve.

  • You may create an account or you can place orders without an account

  • You may use any validly formatted credit card number - either your own, or you can use a credit card generator to create a fake one.

  • Orders placed are submitted to the Upserve POS service and will most likely be rejected after 20 minutes unless someone at Upserve is actively working with this test restaurant

  • payments.upserve.com provides an endpoint for adding payment cards to the vault. The endpoint returns a payment method token which is used by the OLO API. The token should not be reversible and should only be usable to the restaurant it was generated for. The payments sandbox in use for testing is very lenient and will allow invalid card numbers to be used. If you think you've found a bug here we are happy to validate against a live gateway.

• Upserve.com (https://645892349820.vulnerbug.com) is a Wordpress application. Do not test upserve.com directly. Please only test https://645892349820.vulnerbug.com/. Our primary concern here would be defacement or attacks that can be leveraged against other Upserve assets.

• teamhelp.upserve.com is a Wordpress application for internal use by team members. Users are required to sign-in with their Upserve Google account to access the information. There is non-public information on this site. Our primary concern here would be access to non-public information, defacement, or vulnerabilities that would make social engineering more effective.

• Upserve HQ (https://app.upserve.com/partners/) is a Ruby on Rails application used by restaurants to view operational, sales, marketing, and finance information.

  • Credentials are provided by invite only at this time (please don't ask).

  • You are welcome to recon this asset, attempt authentication bypass, and search for anything else of impact.

• Upserve POS HQ (https://hq.breadcrumb.com/) is a Ruby on Rails application used by restaurants to manage their point of sale tablets and view sales reports.

  • Credentials are provided by invite only at this time (please don't ask).

  • You are welcome to recon this asset, attempt authentication bypass, and search for anything else of impact.

• Upserve Inventory (https://inventory.upserve.com) is a PHP application used by restaurants to track and order inventory.

  • Credentials are provided by invite only at this time (please don't ask).

  • You are welcome to recon this asset, attempt authentication bypass, and search for anything else of impact.

• Upserve HQ3 (https://hq.upserve.com) is a React application which wraps our other applications (Upserve HQ, Upserve POS HQ, Upserve Inventory, etc.) in to a single interface.

  • Credentials are provided by invite only at this time (please don't ask).

  • You are welcome to recon this asset, attempt authentication bypass, and search for anything else of impact.

Out of scope vulnerabilities

The following issues are considered out of scope:

• Clickjacking on pages with no sensitive actions.

• Unauthenticated/logout/login CSRF.

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries or software without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• User enumeration or Account oracles -- the ability to submit a phone number, email, UUID and receive back a message indicating an Upserve account exists.

• Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue.

• Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated.

• Banner grabbing issues

• Rate limiting issues

• Missing best practices in email configuration (DMARC, SPF, DKIM, etc)

• DNS issues

Known Issues

The following issues are already known to our team - please do not submit new reports related to them, as they will be considered duplicates.

• Sessions do not expire after password change/reset

• Attacker can enroll credit cards in another user's loyalty accounts

• XML-RPC available on Wordpress sites (and associated DoS issues)

• Subdomain Takeover

Safe Harbor

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act. To the extent your activities are inconsistent with certain restrictions in our Terms & Conditions, we waive those restrictions for the limited purpose of permitting security research under this policy. We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.

If legal action is initiated by a third party against you and you have complied with Upserve's bug bounty policy, Upserve will take steps to make it known that your actions were conducted in compliance with this policy.

Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party may determine whether to pursue legal action. We cannot and do not authorize security research in the name of other entities.

We will not share your report with a third-party without your permission and/or gaining their commitment they will not pursue legal action against you. Please note again that we can’t authorize out-of-scope testing in the name of third parties and such testing is beyond the scope of the program.

Please contact us at bugbounty@upserve.com before engaging in conduct that may be inconsistent with or unaddressed by this policy.

Thank you for helping keep Upserve and our users safe! If you have a question that is not answered on this page, please contact bugbounty@upserve.com

In order to encourage the adoption of bug bounty programs and promote uniform security best practices across the industry, Upserve reserves no rights in this bug bounty policy and so you are free to copy and modify it for your own purposes.