CVE-2026-25758
IDOR in Spree Commerce Guest Checkout Exposes PII
Publication date: 2026-02-06
Last updated on: 2026-02-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| spreecommerce | spree | From 5.1.0 (inc) to 5.1.10 (exc) |
| spreecommerce | spree | From 5.2.0 (inc) to 5.2.7 (exc) |
| spreecommerce | spree | From 5.3.0 (inc) to 5.3.2 (exc) |
| spreecommerce | spree | to 4.10.3 (exc) |
| spreecommerce | spree | From 5.0.0 (inc) to 5.0.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a critical Insecure Direct Object Reference (IDOR) in Spree Commerce's guest checkout flow. It allows any guest user to manipulate address ID parameters to bind arbitrary guest addresses to their order.
As a result, unauthorized users can access other guests' personally identifiable information (PII), such as names, addresses, and phone numbers, bypassing existing ownership validation checks.
This issue affects all guest checkout transactions and has been fixed in versions 4.10.3, 5.0.8, 5.1.10, 5.2.7, and 5.3.2 of Spree Commerce.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive personal information of other customers, including their names, addresses, and phone numbers.
Such exposure of personally identifiable information (PII) can result in privacy breaches, identity theft, and loss of customer trust.
Additionally, it can damage the reputation of the affected e-commerce platform and potentially lead to legal and financial consequences.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Spree Commerce to one of the fixed versions: 4.10.3, 5.0.8, 5.1.10, 5.2.7, or 5.3.2.