CVE-2026-25757
CVE-2026-25757 is a CWE-639 vulnerability in spree_storefront. O3 Security confirms whether CVE-2026-25757 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Unauthenticated Spree Commerce users can view completed guest orders by Order ID
Blast Radius
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.8 |
| 💎RubyGems | spree_storefront | ≥ 5.1.0&&< 5.1.10 | 5.1.10 |
| 💎RubyGems | spree_storefront | ≥ 5.2.0&&< 5.2.7 | 5.2.7 |
| 💎RubyGems | spree_storefront | ≥ 5.3.0&&< 5.3.2 | 5.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_storefront. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether CVE-2026-25757 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
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 detects CVE-2026-25757 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.