Categories
CVE-2026-48009 medium CVSS 6.8

Information Disclosure in shopware/platform (CVE-2026-48009)

Summary

Vulnerability in shopware/platform (CVE-2026-48009). Confidential information can be exposed externally. Exploitable via POST /api/search/user-recovery. Mitigation: upgrade to 6.6.10.18 or later.

Original description

The description as published by the source.

Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a low-privilege admin user with user_recovery:read ACL can take over any admin account by triggering POST /api/_action/user/user-recovery, reading the password recovery hash through POST /api/search/user-recovery, and using PATCH /api/_action/user/user-recovery/password; the root cause is that src/Core/System/User/Recovery/UserRecoveryDefinition.php exposes the hash field through the Admin API without ApiAware(false) or ReadProtection. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

Source: GitHub Security Advisories (Global) 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-48009 has been found in shopware/platform.
Attackers can target a specific entry point like POST /api/search/user-recovery over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade shopware/platform to 6.6.10.18 or later.
If unsure, ask your IT team or search "shopware/platform CVE-2026-48009" on the vendor's site.

CVE-2026-48009 (shopware/platform) — CWE-200 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/search/user-recovery / POST /api/_action/user/user-recovery / PATCH /api/_action/user/user-recovery/password / user_recovery
Patched: 6.6.10.18 — 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

Information disclosure (CWE-200) exists in shopware/platform. Attackers reach the vulnerable code path via POST /api/search/user-recovery.

📍 Affected scope

Check the vendor advisory for the affected versions of shopware/platform. Attack surface: POST /api/search/user-recovery / POST /api/_action/user/user-recovery / PATCH /api/_action/user/user-recovery/password / user_recovery.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 6.6.10.18.

🛡️ 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 POST /api/search/user-recovery requests with malformed payloads or SQL meta-characters. Run grep -r 'shopware/platform' . 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 'shopware/platform' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /api/search/user-recovery' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch
    Upgrade shopware/platform to 6.6.10.18

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

  4. 4
    Post-deployment verification verify
    Replay attack against POST /api/search/user-recovery on staging to confirm patch closes the vector

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

Affected packages

composer shopware/platform
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
composer shopware/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
Packagist shopware/platform
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
Packagist shopware/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]

References

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