CVE-2026-22588
Authenticated IDOR in Spree Allows Unauthorized Address Disclosure
Publication date: 2026-01-08
Last updated on: 2026-02-02
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| spree | spree | to 5.2.5 (exc) |
| spree | spree_api | to 5.2.5 (exc) |
| spreecommerce | spree | to 4.10.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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?
CVE-2026-22588 is an Authenticated Insecure Direct Object Reference (IDOR) vulnerability in the Spree e-commerce platform. It allows an authenticated user to access other users' address information by modifying an order they legitimately own and substituting address identifiers with those belonging to other users. The backend server does not properly verify that the address IDs in the update request belong to the authenticated user, resulting in unauthorized disclosure of sensitive address data. This flaw exists in the order update endpoint during the checkout process and has been fixed by adding strict address ownership validation. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of other users' sensitive address information, potentially exposing personal data such as billing and shipping addresses. An attacker who is authenticated can manipulate their own order to retrieve addresses of other users, which can lead to privacy violations and misuse of personal data. Although it does not affect data integrity or availability, the confidentiality impact is high. This could damage user trust and expose the platform to legal and reputational risks. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and testing the order update API endpoint `/api/v2/storefront/checkout` for unauthorized address ID manipulation. Specifically, an authenticated user can attempt to modify an order they own by sending a PATCH request with billing or shipping address IDs that belong to other users. Detection involves verifying if such requests succeed in associating foreign addresses with the order or if the system properly rejects them. Example commands to test this include: 1. Initialize a shopping cart and obtain a session token with a POST request to `/api/v2/storefront/cart`. 2. Send a PATCH request to `/api/v2/storefront/checkout` with modified `bill_address_attributes` or `ship_address_attributes` containing another user's address ID. If the system returns the other user's address data or updates the order with unauthorized addresses, the vulnerability exists. If the system responds with HTTP status 422 and an error message like "The specified address does not belong to this user.", it indicates the vulnerability is mitigated. These tests require authenticated user credentials and can be scripted using tools like curl or Postman. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, upgrade the Spree e-commerce platform to one of the patched versions: 4.10.2, 5.0.7, 5.1.9, or 5.2.5. These versions include a fix that enforces strict address ownership validation during order updates, preventing users from associating addresses they do not own with their orders. The fix involves validating that any billing or shipping address IDs provided in the order update belong either to the user making the request or are guest addresses (addresses without an associated user). If an unauthorized address ID is detected, the update is rejected with an HTTP 422 error and an appropriate error message. If upgrading immediately is not possible, implement custom validation to check address ownership during order updates to prevent unauthorized address associations. Additionally, monitor API usage for suspicious address ID manipulations and restrict access to authenticated users only. [1, 2, 4, 5]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an authenticated user to access other users' address information without authorization, leading to unauthorized disclosure of sensitive personal data. Such exposure of personal data can violate data protection regulations like GDPR, which require strict controls on personal data access and processing. The vulnerability undermines data confidentiality and privacy, potentially resulting in non-compliance with standards that mandate protection of personally identifiable information (PII). The patch enforces strict ownership validation to prevent unauthorized access, thereby helping maintain compliance with these regulations. [1]