Skip to content

Spree bug bounty programs

spreecommerce.org Updated

Spree runs one public program: a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
1
1 pays cash
Targets in scope
13
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program Spree runs.

Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

13 targets. 6 excluded.

  • https://spreecommerce.org

    Web

  • Email templates and any other place user-supplied content is rendered on the server

    Products and areas

  • Parameter handling across the engine, including permitted attributes and anything reaching mass assignment

    Products and areas

  • Payment method integrations, the payment source records they create and the gateway response handling that decides an order is paid

    Products and areas

  • Product, taxon, variant and stock administration, and the file uploads attached to them

    Products and areas

  • Promotions, discount rules, coupon codes and store credit, plus the calculators behind them

    Products and areas

  • The admin dashboard and the ability definitions that authorise each admin action

    Products and areas

  • The mounted-engine boundary with the host Rails application, covering routing, session sharing and any authentication the host supplies

    Products and areas

  • The order state machine and every checkout step, including address, delivery, payment and confirmation

    Products and areas

  • The policy takes private reports on supported Spree releases, publishing an end-of-life table that defines the window, and it names no component carve-out inside it. The whole engine is in scope

    Products and areas

  • The Spree API, both the storefront and platform namespaces, plus the OAuth application and token model behind them

    Products and areas

  • The storefront controllers and views, the anonymous and customer-authenticated surface a shopper reaches

    Products and areas

  • The user, role and permission model, including guest orders and the order token that authorises access without an account

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 6

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Deployment and hosting configuration choices

  • Host application code a merchant wrote, including decorators and overrides that change Spree's behaviour

  • Payment gateway providers' own systems, which are separate estates

  • Releases outside the published support window, which the end-of-life table defines

  • Third-party Spree extensions maintained outside the core repository

  • Upstream Rails and gem dependency issues, unless Spree's own use of the dependency is what makes the defect reachable

Recent changes

Reward and scope changes across every Spree program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in Spree products, from the NVD.

Search NVD
  • Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 5.0.8, 5.1.10, 5.2.7, and 5.3.2, unauthenticated users can view completed guest orders by Order ID. This issue may lead to disclosure of PII of guest users (including names, addresses and phone numbers). This issue has been patched in versions 5.0.8, 5.1.10, 5.2.7, and 5.3.2.

  • Spree is an open source e-commerce solution built with Ruby on Rails. A critical IDOR vulnerability exists in Spree Commerce's guest checkout flow that allows any guest user to bind arbitrary guest addresses to their order by manipulating address ID parameters. This enables unauthorized access to other guests' personally identifiable information (PII) including names, addresses and phone numbers.

  • Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5, an Unauthenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an unauthenticated attacker to access guest address information without supplying valid credentials or session cookies. This issue has been patched in versions 4.10.2, 5.0.7, 5.1.

  • Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5, an Authenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an authenticated user to retrieve other users’ address information by modifying an existing order. By editing an order they legitimately own and manipulating address identifiers in

  • CVE-2011-10026 Critical

    Spreecommerce versions prior to 0.50.x contain a remote command execution vulnerability in the API's search functionality. Improper input sanitation allows attackers to inject arbitrary shell commands via the search[instance_eval] parameter, which is dynamically invoked using Ruby’s send method. This flaw enables unauthenticated attackers to execute commands on the server.

  • CVE-2011-10019 Critical

    Spreecommerce versions prior to 0.60.2 contains a remote command execution vulnerability in its search functionality. The application fails to properly sanitize input passed via the search[send][] parameter, which is dynamically invoked using Ruby’s send method. This allows attackers to execute arbitrary shell commands on the server without authentication.

  • CVE-2021-41275 Critical

    spree_auth_devise is an open source library which provides authentication and authorization services for use with the Spree storefront framework by using an underlying Devise authentication framework. In affected versions spree_auth_devise is subject to a CSRF vulnerability that allows user account takeover. All applications using any version of the frontend component of spree_auth_devise are affe

  • Spree is a complete open source e-commerce solution built with Ruby on Rails. In Spree from version 3.7 and before versions 3.7.13, 4.0.5, and 4.1.12, there is an authorization bypass vulnerability. The perpetrator could query the API v2 Order Status endpoint with an empty string passed as an Order token. This is patched in versions 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Us

About this page

This page gathers every public program listed under spreecommerce.org: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.