CVE-2026-25757 — spree_storefront
Fix: spree/spree@3e00be6CVE-2026-25757 is a CWE-639 vulnerability in spree_storefront. A fix is available for spree_storefront — see the affected versions and patch details below.
Unauthenticated Spree Commerce users can view completed guest orders by Order ID
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25757.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
spree_storefront💎spree_storefront💎spree_storefront💎spree_storefrontReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 5.0.8, 5.1.10, 5.2.7, and 5.3.2, unauthenticated users can view completed guest orders by Order ID. This issue may lead to disclosure of PII of guest users (including names, addresses and phone numbers). This issue has been patched in versions 5.0.8, 5.1.10, 5.2.7, and 5.3.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | spree_storefront | all versions | 5.0.8bundle update spree_storefront --conservative |
| 💎RubyGems | spree_storefront | ≥ 5.1.0&&< 5.1.10 | 5.1.10bundle update spree_storefront --conservative |
| 💎RubyGems | spree_storefront | ≥ 5.2.0&&< 5.2.7 | 5.2.7bundle update spree_storefront --conservative |
| 💎RubyGems | spree_storefront | ≥ 5.3.0&&< 5.3.2 | 5.3.2bundle update spree_storefront --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_storefront, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update spree_storefront to 5.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25757 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-25757 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-25757. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-25757 in your dependencies?
O3 Security finds CVE-2026-25757 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.