CVE-2020-26223: Spree is a complete open source e-commerce solution built with Ruby on Rails

This month

HIGH 7.7UPGRADE

CVE-2020-26223 is a high-severity flaw (CVSS 7.7) affecting spree. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spree is a complete open source e-commerce solution built with Ruby on Rails. In Spree from version 3.7 and before versions 3.7.13, 4.0.5, and 4.1.12, there is an authorization bypass vulnerability. The perpetrator could query the API v2 Order Status endpoint with an empty string passed as an Order token. This is patched in versions 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-863
Published	2020-11-13
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: spreecommerce

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-11-13 18:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

spreecommerce spree UPGRADE

Affected: >= 3.7.0 and < 3.7.13 · >= 4.0.0 and < 4.0.5 · >= 4.1.0 and < 4.1.12

Fixed in: 3.7.13, 4.0.5, 4.1.12

Safe to downgrade to: a release before 3.7.0

1. Check installed version

apt-cache policy spree || rpm -q spree || spree --version

2. UPGRADE to 3.7.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spree

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spree

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.7.0 (Debian / Ubuntu)

apt-cache madison spree sudo apt install spree=<VERSION_BEFORE_3.7.0> sudo apt-mark hold spree

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spree sudo dnf downgrade spree-<VERSION_BEFORE_3.7.0> sudo dnf versionlock add spree

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-26223?

spree: upgrade to 3.7.13, 4.0.5, 4.1.12. Exact commands for each OS are on this page.

Is CVE-2020-26223 being exploited?

CVE-2020-26223 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-26223 affect?

CVE-2020-26223 affects spree. Severity is high (CVSS 7.7). Spree is a complete open source e-commerce solution built with Ruby on Rails. In Spree from version 3.7 and before versions 3.7.13, 4.0.5, and 4.1.12, there is an authorization bypass vulnerability. The perpetrator could query the API v2 Or

How urgent is CVE-2020-26223?

Priority 49/100. High severity; Public exploit reference

Software pages

Ruby on Rails vulnerabilities · Ruby vulnerabilities

Related CVEs

CVE-2011-10019 CRITICAL 9.8 UPGRADE Spreecommerce versions prior to 0.60.2 contains a remote command execution vulnerability in its search functio
CVE-2026-25758 HIGH 7.5 UPGRADE Spree is an open source e-commerce solution built with Ruby on Rails
CVE-2026-25757 MEDIUM 5.3 UPGRADE Spree is an open source e-commerce solution built with Ruby on Rails
CVE-2026-22588 MEDIUM 6.5 UPGRADE Spree is an open source e-commerce solution built with Ruby on Rails
CVE-2020-15269 HIGH 7.4 UPGRADE In Spree before versions 3.7.11, 4.0.4, or 4.1.11, expired user tokens could be used to access Storefront API

References

← Back to latest CVEs