# CVE-2011-10026: Spreecommerce < 0.50.x API RCE

> Unauthenticated attackers can execute arbitrary shell commands on the server via improper input sanitation in the API search functionality.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-x485-rhg3-cqr4

## What is CVE-2011-10026?

CVE-2011-10026 is a critical command injection vulnerability in Spreecommerce, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2011-10026?

4 open source packages ship an affected version, including rd_searchlogic and spree. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rd_searchlogic` | RubyGems | All versions to 3.0.1 | None |
| `rd_searchlogic` | RubyGems | All versions to 3.0.1 | None |
| `spree` | RubyGems | From 0.30.0.beta1 | 0.50.0 |
| `spree` | RubyGems | From 0.30.0.beta1 | 0.50.0 |

Products: Spreecommerce Spree.

## How do I fix CVE-2011-10026?

Upgrade to a fixed version.

## Is CVE-2011-10026 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-10026 exists.

Public exploit code:

- Spreecommerce Arbitrary Command Execution (metasploit)

## Other vulnerabilities in Spreecommerce

- [CVE-2011-10019](https://insights.sbomify.com/CVE-2011-10019/): Spreecommerce < 0.60.2 Search Parameter RCE (critical 10.0)
- [CVE-2026-25757](https://insights.sbomify.com/CVE-2026-25757/): Unauthenticated Spree Commerce users can view completed guest orders by Order ID (high 7.7)
- [CVE-2026-25758](https://insights.sbomify.com/CVE-2026-25758/): Spree allows unauthenticated users can access all guest addresses (high 7.7)
- [CVE-2020-26223](https://insights.sbomify.com/CVE-2020-26223/): Authorization bypass in Spree (high 7.7)
- [CVE-2026-22589](https://insights.sbomify.com/CVE-2026-22589/): Spree API has Unauthenticated IDOR - Guest Address (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-10026 and fix it if it is affected.

What it is: CVE-2011-10026 is a critical command injection vulnerability in Spreecommerce, published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-10026 exists.

Affected packages and fixed versions:
- rd_searchlogic (RubyGems): affected all versions up to 3.0.1; no fix listed
- rd_searchlogic (RubyGems): affected all versions up to 3.0.1; no fix listed
- spree (RubyGems): affected from 0.30.0.beta1; fixed in 0.50.0
- spree (RubyGems): affected from 0.30.0.beta1; fixed in 0.50.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-10026/ (Markdown: https://insights.sbomify.com/CVE-2011-10026/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-10026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-10026
- OSV: https://osv.dev/vulnerability/CVE-2011-10026

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-10026/
Summaries are generated and may contain mistakes; the official description above is the record.