Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification
Date: 2026-01
Affected: rubygems/spree_api, rubygems/spree_api, rubygems/spree_api
Attack vector: auth-bypass
Category: vulnerability-disclosure
Severity: Medium
CVE: CVE-2026-22588
CWE: CWE-639
CVSS: 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)

### Summary An Authenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an authenticated user to retrieve other users’ address information by modifying an existing order. By editing an order they legitimately own and manipulating address identifiers in the request, the backend server accepts and processes references to addresses belonging to other users, subsequently associating those addresses with the attacker’s order and returning them in the response. ### Details Affected Component(s) - Authenticated user order management - Address association logic - Order update endpoint(s) Affected Endpoint(s): - `/api/v2/storefront/checkout` The application fails to enforce proper object-level authorization when updating an existing order. While the user is authenticated and authorized to modify their own order, the backend does not verify that the supplied address identifiers belong to the same authenticated user. ### PoC Preconditions - Valid authenticated user account Step 1: Log-in using a valid user, in this case customer2@example.com Step 2: Visualize current user’s addresses **Request** GET `/account/addresses` The following screenshot shows customer2@example.com address. <img width="336" height="375" alt="User Address" src="https://github.com/user-attachments/assets/ceb1f214-7ac0-40b0-af22-6fe9d21254bb" /> Step 3: Initialize the Shopping Cart **Request** POST `/api/v2/storefront/cart HTTP/1.1` From the response, extract the tok


Mitigations:

Architectural layers (MAESTRO):