Skip to content
Noroxi
CVE-2026-25758· NVD / CVE Program· CNA GitHub_M

Spree allows unauthenticated users can access all guest addresses

Spree is an open source e-commerce solution built with Ruby on Rails. A critical IDOR vulnerability exists in Spree Commerce's guest checkout flow that allows any guest user to bind arbitrary guest addresses to their order by manipulating address ID parameters. This enables unauthorized access to other guests' personally identifiable information (PII) including names, addresses and phone numbers. The vulnerability bypasses existing ownership validation checks and affects all guest checkout transactions. This vulnerability is fixed in 4.10.3, 5.0.8, 5.1.10, 5.2.7, and 5.3.2.

HighCVSS 7.7 · v4.0—No exploit Fix available
Published
Feb 6, 2026
Updated
Jun 17, 2026
EPSS
0.7% · 51th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.7
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
spreecommercespree

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • spreecommerce spreebefore 4.10.3
  • spreecommerce spree5.0.0 and later · before 5.0.8
  • spreecommerce spree5.1.0 and later · before 5.1.10
  • spreecommerce spree5.2.0 and later · before 5.2.7
  • spreecommerce spree5.3.0 and later · before 5.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • spree spree

    • < 4.10.3, >= 5.0.0, < 5.0.8, >= 5.1.0.beta, < 5.1.10, >= 5.2.0.rc1, < 5.2.7, >= 5.3.0.rc2, < 5.3.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
RubyGemsspree_apifrom 5.0.0 · before 5.0.85.0.8
RubyGemsspree_apifrom 5.1.0 · before 5.1.105.1.10
RubyGemsspree_apifrom 5.2.0 · before 5.2.75.2.7
RubyGemsspree_apifrom 5.3.0 · before 5.3.25.3.2
RubyGemsspree_apibefore 4.10.34.10.3

Other highest-scoring records for the same primary product.

  • CVE-2011-10019Spreecommerce < 0.60.2 Search Parameter RCE
    42Plan
  • CVE-2011-10026Spreecommerce < 0.50.x API RCE
    38Monitor
  • CVE-2026-25757Unauthenticated Spree Commerce users can view completed guest orders by Order ID
    30Monitor
  • CVE-2026-22589Spree API has Unauthenticated IDOR - Guest Address
    30Monitor
  • CVE-2026-22588Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification
    26Monitor
  • CVE-2020-26223Authorization bypass in Spree
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
spree spree4.10.3 · descriptionVendor (CNA)
RubyGems:spree_api4.10.3Package registry (OSV)
RubyGems:spree_api5.0.8Package registry (OSV)
RubyGems:spree_api5.1.10Package registry (OSV)
RubyGems:spree_api5.2.7Package registry (OSV)
RubyGems:spree_api5.3.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records