Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-94462 high CVSS 7.1

Vulnerability in spree_api (CVE-2026-94462)

Summary

Vulnerability in spree_api (CVE-2026-94462). Confidential information can be exposed externally. Exploitable via PATCH /api/v3/store/carts/. Mitigation: upgrade to 5.5.4 or later.

Original description

The description as published by the source.

Summary

The Store API v3 endpoint PATCH /api/v3/store/carts/:id/associate binds a guest cart to the authenticated caller without verifying possession of that cart. It locates the cart by prefixed ID only — current_store.carts.where(user: [nil, current_user]).find_by_prefix_id!(params[:id]) — and omits the authorize!(:update, @cart, cart_token) check that every other action in the controller performs via CartResolvable. Because prefixed IDs are a reversible Sqids encoding of the auto-increment primary key (obfuscation, not a token), an authenticated customer can name arbitrary guest cart IDs, take them over, and read the checkout addresses stored on them. This is broken access control / IDOR, reachable by any low-privilege registered user.

Severity

Requires an authenticated store account and depends on target guest carts already carrying an address and not yet being associated, on a store not running in login_required mode. Confidentiality impact is the driver (guest checkout PII); integrity impact is limited and recoverable (cart reassignment + email overwrite on an in-progress cart). Not Critical: the action is gated behind authentication (PR:L, not PR:N) and constrained by cart state, so it is not anonymously exploitable.

Details

Root cause: associate skips the cart-possession check its sibling actions enforce and trusts a guessable identifier as the sole locator.

Entry point. Spree::Api::V3::Store::CartsController#associate (`carts_…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-94462 has been found in spree_api.
Attackers can target a specific entry point like PATCH /api/v3/store/carts/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade spree_api to 5.5.4 or later.
If unsure, ask your IT team or search "spree_api CVE-2026-94462" on the vendor's site.

CVE-2026-94462 (spree_api) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v3/store/carts/ / POST /api/v3/store/auth/login / CartResolvable / login_required
Patched: 5.5.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in spree_api. Attackers reach the vulnerable code path via PATCH /api/v3/store/carts/.

📍 Affected scope

Check the vendor advisory for the affected versions of spree_api. Attack surface: PATCH /api/v3/store/carts/ / POST /api/v3/store/auth/login / CartResolvable / login_required.

🔥 Severity

Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.5.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PATCH /api/v3/store/carts/ requests with malformed payloads or SQL meta-characters. Run grep -r 'spree_api' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'spree_api' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で spree_api を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PATCH /api/v3/store/carts/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PATCH /api/v3/store/carts/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade spree_api to 5.5.4

    ステージング環境で 5.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PATCH /api/v3/store/carts/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

rubygems spree_api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.5.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details