CVE-2011-10019

Spreecommerce Spree code injection

9.8 CRITICALPublic exploitEPSS 5.76%

Published13 Aug 2025

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Spreecommerce Spree< 0.60.2

Remediation

Fixed in

Spreecommerce Spree≥ 0.60.2

References

https://github.com/orgs/spreeProduct
https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/spree_search_exec.rbExploitThird Party Advisory
https://web.archive.org/web/20111009192436/http://spreecommerce.com/blog/2011/10/05/remote-command-product-group/Release Notes
https://www.exploit-db.com/exploits/17941ExploitVDB Entry
https://www.vulncheck.com/advisories/spreecommerce-search-parameter-rceThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2011-10019 being actively exploited?

CVE-2011-10019 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 5.76%.

How severe is CVE-2011-10019?

CVE-2011-10019 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 5.76% probability of exploitation.

Which products are affected by CVE-2011-10019?

Affected products include Spreecommerce Spree.

How do I fix CVE-2011-10019?

Upgrade affected software to a fixed version, for example Spreecommerce Spree 0.60.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2011-10019 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.