# CVE-2011-10026: Spree Commerce is vulnerable to RCE through Search API

Source: https://junglewise.ai/threats/cve-2011-10026-spree-commerce-is-vulnerable-to-rce-through-search-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-08-20  
License: CC BY 4.0 with a link back

CVE-2011-10026 · Severity: medium · CVSS 4 · Published 2025-08-20

Spree Commerce is vulnerable to RCE through Search API

Technologies: [spree (RubyGems)](https://junglewise.ai/threats/technologies/spree). Vendors: [RubyGems](https://junglewise.ai/threats/vendors/rubygems).

## Quick answers

**Is CVE-2011-10026 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2011-10026 being exploited in the wild.

**How severe is CVE-2011-10026?** Medium severity, with a CVSS score of 4, published 20 August 2025.

**Which products and versions are affected?** rd_searchlogic (RubyGems) ECOSYSTEM:introduced=0,last_affected=3.0.1; spree (RubyGems) ECOSYSTEM:introduced=0.30.0.beta1,fixed=0.50.0.

**Is there a fix for CVE-2011-10026?** Yes. spree (RubyGems): upgrade to 0.50.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2011-10026?** Check whether you run rd_searchlogic (RubyGems) or spree (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- spree (RubyGems): upgrade to 0.50.0 or later

  ```sh
  bundle update spree
  ```


## Affected products

- rd_searchlogic (RubyGems) ECOSYSTEM:introduced=0,last_affected=3.0.1
- spree (RubyGems) ECOSYSTEM:introduced=0.30.0.beta1,fixed=0.50.0

## Identifiers

- CVE-2011-10026
- GHSA-x485-rhg3-cqr4

## Related threats

- [Spree has Remote Command Execution vulnerability in search functionality](https://junglewise.ai/threats/cve-2011-10019-spree-has-remote-command-execution-vulnerability-in-search)
- [Spree does not properly restrict the use of a hash to provide values for a model's attributes](https://junglewise.ai/threats/cve-2008-7310-spree-does-not-properly-restrict-the-use-of-a-hash-to-provide)
- [Spree uses a hardcoded hash value](https://junglewise.ai/threats/cve-2008-7311-spree-uses-a-hardcoded-hash-value)
- [Spree allows remote attackers to obtain sensitive information](https://junglewise.ai/threats/cve-2010-3978-spree-allows-remote-attackers-to-obtain-sensitive-information)
- [Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls](https://junglewise.ai/threats/cve-2020-15269-ensure-that-doorkeeper-token-is-valid-when-authenticating)
