CVE-2011-10019

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 69.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.8
EG Score
9.8(medium)
EPSS
89.5%
KEV
Not listed

Published

August 13, 2025

Last Modified

September 24, 2025

Advisory Details (4)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

Spreecommerce < 0.60.2 Search Parameter RCE | Advisories | VulnCheck

https://www.vulncheck.com/advisories/spreecommerce-search-parameter-rce
generic

Spree 0.60.2 Released (Security Fix) | Spree Commerce

https://web.archive.org/web/20111009192436/http://spreecommerce.com/blog/2011/10/05/remote-command-product-group/
generic
https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/spree_search_exec.rb
generic

Spree Commerce · GitHub

https://github.com/orgs/spree

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
spree0.0.5 ... 0.9.4 (50 versions)0.60.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:54 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 01:55 UTCEPSS rescore
  4. 2026-07-13 22:25 UTCEPSS rescore
  5. 2026-07-13 06:08 UTCEPSS rescore
  6. 2026-07-11 08:22 UTCEPSS rescore
  7. 2026-07-11 08:22 UTCEPSS rescore
  8. 2026-07-08 15:10 UTCEPSS rescore
  9. 2026-07-08 15:10 UTCEPSS rescore
  10. 2026-07-06 16:23 UTCEPSS rescore
  11. 2026-07-06 02:19 UTCEPSS rescore
  12. 2026-07-06 02:19 UTCEPSS rescore
  13. 2026-07-05 02:26 UTCEPSS rescore
  14. 2026-07-04 06:27 UTCEPSS rescore
  15. 2026-07-02 14:01 UTCEPSS rescore
  16. 2026-07-01 15:02 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-06-30 23:19 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-28 14:03 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-28 04:52 UTCEPSS rescore
  23. 2026-06-27 03:05 UTCEPSS rescore
  24. 2026-06-27 03:05 UTCEPSS rescore
  25. 2026-06-25 13:46 UTCEPSS rescore
Show 37 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-22 14:22 UTCEPSS rescore
  6. 2026-06-22 14:22 UTCEPSS rescore
  7. 2026-06-21 01:56 UTCEPSS rescore
  8. 2026-06-21 01:56 UTCEPSS rescore
  9. 2026-06-19 19:22 UTCEPSS rescore
  10. 2026-06-19 19:22 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-15 17:44 UTCEPSS rescore
  18. 2026-06-13 22:57 UTCEPSS rescore
  19. 2026-06-13 22:57 UTCEPSS rescore
  20. 2026-06-12 23:08 UTCEPSS rescore
  21. 2026-06-10 22:14 UTCEPSS rescore
  22. 2026-06-10 13:17 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-06 13:44 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:07 UTCEPSS rescore
  29. 2026-06-04 13:09 UTCEPSS rescore
  30. 2026-06-04 13:09 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-31 00:14 UTCEPSS rescore
  35. 2026-05-30 00:23 UTCEG score recompute
  36. 2026-05-29 13:41 UTCEPSS rescore
  37. 2026-05-29 13:40 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/multi/http/spree_search_exec✓ verified
    First seen Oct 5, 2011

    Spreecommerce 0.60.1 Arbitrary Command Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-10019?
CVE-2011-10019 is a critical vulnerability published on August 13, 2025. 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…
When was CVE-2011-10019 disclosed?
CVE-2011-10019 was first published in the National Vulnerability Database on August 13, 2025, with the most recent update on September 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-10019 actively exploited?
CVE-2011-10019 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2011-10019?
CVE-2011-10019 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2011-10019?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-10019, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2011-10019

Explore →

Is Your Infrastructure Affected by CVE-2011-10019?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs