NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
MEDIUM severity

CVE-2020-26223 — spree_api

MEDIUMFix: spree/spree#10573

CVE-2020-26223 is a medium-severity (CVSS 6.5) CWE-863 vulnerability in spree_api. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for spree_api — see the affected versions and patch details below.

Authorization bypass in Spree

Also known asGHSA-m2jr-hmc3-qmpr
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.00%0.54%1.08%1.62%0.3%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
💎spree_api💎spree_api💎spree_api

Real-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

Impact

The perpetrator could query the API v2 Order Status endpoint with an empty string passed as an Order token

Patches

Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected.

References

Pull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsspree_api≥ 3.7.0&&< 3.7.133.7.13bundle update spree_api --conservative
💎RubyGemsspree_api≥ 4.0.0&&< 4.0.54.0.5bundle update spree_api --conservative
💎RubyGemsspree_api≥ 4.1.0&&< 4.1.124.1.12bundle update spree_api --conservative

Affected Products

1 product · 3 configurations
Application
spreespreecommerce
≥ 4.1.0 && < 4.1.12
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Spree is a complete open source e-commerce solution built with Ruby on R…

github.comNVDNov 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update spree_api to 3.7.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-26223 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The perpetrator could query the [API v2 Order Status](https://guides.spreecommerce.org/api/v2/storefront#tag/Order-Status) endpoint with an empty string passed as an Order token ### Patches Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected. ### References Pull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573 ### For more information If you have any questions or comments about this advisory: * Email us at [[email protected]](mailto:[email protected])
O3 Security · Impact-Aware SCA

Is CVE-2020-26223 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-26223: spree_api — Fixed in 3.7.13