CVE-2020-26223

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

1.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-11-13 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:07 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.1% in the next 30 days (EPSS).
• Severity: 7.7 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-11-13 18:15 UTC

Last modified

2026-06-17 03:07 UTC

Exploit probability

1.1% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Modified

Affected

• Spreecommerce Spree < 3.7.13
• Spreecommerce Spree < 4.0.5
• Spreecommerce Spree < 4.1.12

Attack profile CVSS 3.1 · 7.7

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-26223.md and follow it. Check whether this project is affected by CVE-2020-26223. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge