Security Contact

We are intensely focused on keeping our customers’ data safe and secure here at FoxyCart. Any input that helps us better serve and protect our customers is welcome.

Security at Foxy

Security is core to what we do. Foxy processes payments for thousands of merchants, and we work with independent security researchers to find and fix weaknesses before attackers do. If you believe you've found a security issue in Foxy, we want to hear about it, and we pay for real findings.

This page is our vulnerability disclosure policy. Read it in full before testing. Reports that ignore it are closed without reward.

How to report

  • Email: security@foxy.io. Please encrypt sensitive details with our PGP key (fingerprint FA39 752C 4CBA DD15 F964 9575 29C4 9298 D941 B672).

  • Open Bug Bounty: non-intrusive findings (XSS, CSRF, open redirect, improper access control) may also be submitted through our Open Bug Bounty program.

  • Intrusive findings (SSRF, SQL injection, RCE, request smuggling, subdomain takeover, etc.) must be sent by email. Open Bug Bounty does not accept them.

What a valid report looks like

Every report must:

  • Describe a real, exploitable security impact on Foxy or its users, in your own words: what an attacker gains, and under what conditions.

  • Include step-by-step reproduction against an account or store you created, plus a working proof of concept (raw requests and responses, video, or screenshots) that reproduces in a current browser.

  • Include a CVSS vector that matches the impact you actually demonstrated, not a theoretical worst case. We re-rate every report; inflated severity is not a basis for negotiation.

  • Cover one issue per report. If you chain issues, submit the chain as one report.

We close the following without reward:

  • Output from automated scanners, or reports generated by AI tools without manual verification.

  • Theoretical issues without a working proof of concept.

  • Reports that misidentify the vulnerability (see the notes on CSRF and XSS below).

  • Best-practice or configuration findings with no demonstrated impact.

  • Anything listed below under "By design" or "Exclusions."

  • Duplicates. The first valid report wins, including issues we already found internally.

Please don't ask about payment before we've validated your report.

Scope

In scope

  • admin.foxycart.com

  • admin.foxy.io

  • auth.foxy.io

  • api.foxycart.com

  • api-sandbox.foxycart.com

  • foxy-demo.foxycart.com

  • Stores you create yourself on *.foxycart.com (cart, checkout, receipt, customer portal)

  • Subdomain takeover of any foxy.io or foxycart.com subdomain (proof required: serve a file you control from the subdomain)

Out of scope

  • Foxy merchants' stores, websites and applications. Do not test our customers. Create your own free store instead.

  • www.foxy.io (hosted on Storyblok) and wiki.foxycart.com (DokuWiki). Issues in these third-party platforms should be reported to their vendors. Issues caused by Foxy's own configuration of them may be eligible for Hall of Fame recognition, but not cash rewards.

  • Any other third-party service Foxy uses (help desk, email, payment gateways, etc.).

How to test

  1. Create a free account at admin.foxycart.com/signup. Include "security" or your researcher handle in your name or email address, and name your store subdomain yourhandle-security.

  2. Use test payment gateways and test card numbers only (for example, 4111 1111 1111 1111). Never use real cardholder data.

  3. To test the API, create an API client from the Integrations page in the admin, or at api-sandbox.foxycart.com. The API uses OAuth 2.0.

  4. Full documentation is at wiki.foxycart.com and api.foxycart.com/docs.

Rules of engagement

  • Only interact with accounts and stores you own. If you encounter another user's data, stop, do not keep it, and report it immediately.

  • No automated scanners, high-volume fuzzing, or aggressive scripts.

  • No denial of service, spam, social engineering or phishing of Foxy staff or contractors, or physical attacks.

  • Do not degrade service for other users, or modify or destroy data you don't own.

Intrusive findings: minimum proof, then stop

  • SQL injection: show the database version or a boolean/time-based proof. Do not extract, modify, or delete data.

  • Remote code execution: run a harmless command (id, hostname). No persistence, lateral movement, or reverse shells left running.

  • SSRF: show the response from an internal or metadata endpoint. Do not use any credentials you obtain.

  • Subdomain takeover: serve a harmless text file containing your handle at an unguessable path. No other content. Release the resource when we ask.

  • Delete any data you obtained once your report is submitted. Going beyond the minimum proof may reduce or void a reward.

By design: how Foxy works

Most invalid reports we receive are about intentional features. Please understand these before reporting:

  • Add-to-cart parameters are client-controlled. Products are added to the cart via GET or POST, and the name, price, and other options can be modified. This is by design. Merchants protect their links and forms with HMAC cart validation. Price manipulation on a store without HMAC validation enabled is not a vulnerability. A bypass of HMAC validation is, and we'd love to see it.

  • Cart requests can be sent from any origin, including non-HTTPS pages, and do not use CSRF tokens (aside from HMAC validation above).

  • Merchant templates can contain arbitrary JavaScript. Cart, checkout, receipt and email templates, and some language strings, accept whatever HTML and JavaScript the merchant chooses. A merchant injecting script into their own store is not XSS.

  • Remote fetches. Our image cache and template caching features make outbound requests to URLs the merchant provides. This is by design. It's only SSRF if you demonstrate access to internal or otherwise privileged resources.

Exclusions

The following are not eligible for rewards, unless you demonstrate a concrete, real-world exploit beyond the item as described.

Email and DNS

  • Missing or misconfigured SPF, DKIM, or DMARC records on any domain, and email spoofing.

  • Dangling DNS records or "possible" subdomain takeovers without an actual takeover.

  • Lookalike or unregistered domains we don't own.

General web

  • Self-XSS, and issues exploitable only through self-XSS.

  • XSS that requires modifying headers a victim's browser won't send (for example, Referer).

  • Missing security headers (HSTS, CSP, X-Frame-Options, etc.), cookie flags, or permissive CORS on endpoints without sensitive data.

  • Clickjacking on pages without a sensitive, state-changing action.

  • CSRF on forms available to anonymous users, and logout CSRF.

  • Open redirects without a chained impact (such as token theft).

  • Host header injection without a demonstrated impact such as cache poisoning or leaking a password reset token to an attacker-controlled host.

  • Version or banner disclosure, stack traces, non-200 error pages, normal OPTIONS responses, publicly known files (robots.txt, etc.).

  • TLS cipher or protocol findings from automated tools without a practical exploit. BREACH, unless you show our mitigation is insufficient.

  • Browser autocomplete or "save password" behavior.

  • Tabnabbing without a specific, realistic exploit.

  • CSV/formula injection in exported files.

Authentication and accounts

  • No maximum password length. This is not a denial of service.

  • Missing rate limiting or CAPTCHA, unless you demonstrate account compromise or significant impact. Please don't automate high volumes of requests to test this.

  • Account or email enumeration via login, signup, or password reset responses.

  • Admin signup without CAPTCHA or email verification.

  • Password reuse, password complexity, and similar policy preferences.

Infrastructure

  • Internal IP addresses revealed by AWS load balancers on redirected requests. These are AWS addresses, not ours.

  • Denial of service of any kind, including Slowloris and resource-exhaustion claims.

  • Third-party scripts loaded in the admin.

Leaked credentials and open source

  • API keys or tokens our merchants have exposed publicly (GitHub, Pastebin, etc.). We appreciate these reports, especially for live accounts, and may reward them, but can't promise to.

  • Known vulnerable dependency versions in our open source repositories, unless you demonstrate an exploit against Foxy. We're notified of these automatically.

  • Exploits that require an already-compromised site, browser, or device, or a malicious merchant attacking their own store.

A note about CSRF

If your proof of concept includes a valid CSRF token, it is not a CSRF vulnerability. If you can obtain a victim's CSRF token, show that. We'll close CSRF reports that include the token without further investigation.

A note about XSS

Make sure your XSS actually executes in a current, unmodified browser, not just in Burp Suite or another proxy. If we can't reproduce it in a browser, we'll treat it as self-XSS.

Rewards

We pay cash for validated issues with demonstrated impact. Amounts are based on real exploitability in our environment, not on scanner output or self-assigned severity.

Severity

Reward

Examples

Critical

$1,000–$2,500

Cross-store data access, account takeover without user interaction, exposure of payment or customer data at scale, remote code execution

High

$400–$1,000

Stored XSS executing in another user's admin session, IDOR against another store, SSRF reaching internal resources, actual subdomain takeover

Medium

$100–$300

Issues with real but limited impact, or requiring significant user interaction

Low

At our discretion: Hall of Fame; cash

Minor issues with a demonstrated security impact

Informational

None

Best-practice findings, known issues, by-design behavior, duplicates

  • Clear reports with root-cause analysis and a working fix suggestion may receive a bonus.

  • Final severity and reward amounts are at Foxy's discretion.

  • Foxy employees, contractors, and their immediate families are not eligible. We cannot pay researchers in countries subject to sanctions.

  • Researchers who repeatedly submit low-quality, out-of-scope, or AI-generated reports will be ignored.

What we do

  • Acknowledge your report within 3 business days.

  • Validate and assign severity within 10 business days, and keep you updated on progress.

  • Fix validated issues and pay any reward after validation.

  • Credit you in our Hall of Fame (unless you'd prefer not to be named).

Disclosure

Give us a reasonable amount of time to fix an issue before disclosing it publicly or to any third party, and don't disclose without our written permission. Reports submitted through Open Bug Bounty are also subject to Open Bug Bounty's disclosure rules.

Safe harbor

If you make a good-faith effort to follow this policy, we consider your research authorized, will not pursue or support legal action against you, and will work with you to understand and resolve the issue. If you're unsure whether something is allowed, email us before testing.

Archived Hall of Fame

FoxyCart Application Disclosures

3rd Party System Disclosures