Pii-Exposure - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/pii-exposure/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 23 Sep 2026 01:54:53 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgIDOR Vulnerability in Spree API Associate Endpointhttps://feed.craftedsignal.io/briefs/2026-09-spree-idor/Wed, 23 Sep 2026 01:54:53 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-spree-idor/An Insecure Direct Object Reference (IDOR) vulnerability in the Spree API v3 allows authenticated users to associate and exfiltrate PII from arbitrary guest carts using reversible Sqids identifiers.Spree versions 5.4.0 through 5.4.3 and 5.5.0 through 5.5.3 contain a high-severity Insecure Direct Object Reference (IDOR) vulnerability in the PATCH /api/v3/store/carts/:id/associate endpoint. The vulnerability arises because the controller fails to perform the standard authorize!(:update, @cart, cart_token) check for the association process. Instead, it relies on a prefixed_id which is generated via reversible Sqids encoding of sequential database primary keys. An authenticated store user can derive candidate cart IDs offline and iterate through them, associating victim guest carts to their own account. Successful exploitation permits the attacker to read sensitive customer checkout information, including full names, street addresses, and phone numbers stored in the guest cart objects.

Attack Chain

  1. Attacker registers an ordinary customer account on the target Spree storefront.
  2. Attacker logs into the store via POST /api/v3/store/auth/login to obtain a valid session JWT.
  3. Attacker uses the known Sqids algorithm and target sequential database IDs to generate a list of candidate prefixed_id strings (e.g., cart_XXXXXXXXXX).
  4. Attacker iterates through the generated list, sending PATCH /api/v3/store/carts/:id/associate requests for each candidate ID.
  5. The backend controller processes the request, locates the guest cart via find_cart_for_association, and skips the required authorization check.
  6. The Spree.cart_associate_service reassigns the guest order to the attacker's account and overwrites the associated email address.
  7. The API returns a 200 OK response containing the serialized customer PII (billing and shipping addresses) previously stored on the victim's guest cart.

Impact

Successful exploitation results in the unauthorized exposure of personally identifiable information (PII) including names, physical addresses, and contact details for store guests. Furthermore, it causes a disruption to the original guest's shopping experience as their in-progress cart is hijacked and reassigned to the attacker's account. This affects any Spree-based storefront not running in login_required mode.

Recommendation

Prioritized actions for administrators:

  • Upgrade Spree backend components to version 5.4.4 or 5.5.4 immediately to address CVE-2026-94462.
  • Audit access logs for high-frequency PATCH requests to the /api/v3/store/carts/ endpoint originating from single authenticated user sessions.
  • Monitor for anomalous 404 or 422 error patterns on the association endpoint which may indicate automated ID enumeration attempts.
]]>highthreatidorbroken-access-controlspreepii-exposure