CVE-2011-10026 affects Spree Commerce versions prior to 0.50.x. The vulnerability is in the API search functionality, where user-controlled input supplied via the search[instance_eval] parameter is insufficiently sanitized and is dynamically invoked through Ruby's send method. This unsafe handling allows an attacker to inject arbitrary shell commands through the search interface. Because the vulnerable API can be reached without authentication, a remote attacker can exploit the flaw over the network to achieve command execution on the underlying server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/multi/http/spree_searchlogic_exec.rb) that exploits an arbitrary command execution vulnerability in Spreecommerce versions 0.50.0 and earlier (CVE-2011-10026). The exploit leverages unvalidated input in the API's searchlogic functionality, which is passed to Ruby's 'send' method, allowing attackers to execute arbitrary system commands via a specially crafted GET request to the /api/orders.json endpoint. The module is written in Ruby and is structured as a standard Metasploit exploit, requiring the attacker to specify the base URI of the target Spreecommerce site. The exploit sends a GET request with a malicious 'search[instance_eval]' parameter, triggering command execution on the server. The payload is a command string, and the exploit is operational, providing remote code execution capabilities. The only fingerprintable endpoints are the base URI and the vulnerable API endpoint. The repository is a typical Metasploit module, with all logic contained in a single file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.