← Back
CVE-2026-48015 medium CVSS 4.9

Cross-Site Scripting (XSS) in shopware/core (CVE-2026-48015)

Summary

cross-site scripting in shopware/core (CVE-2026-48015). Confidential information can be exposed externally. Exploitable via ``allowed_extensions``. Mitigation: upgrade to `6.6.10.18` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-48015** has been found in shopware/core. Attackers can target a specific entry point like ``allowed_extensions`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 4.9/10. What to do: upgrade shopware/core to **6.6.10.18** or later. If unsure, ask your IT team or search "shopware/core CVE-2026-48015" on the vendor's site.
CVE-2026-48015 (shopware/core) — CWE-79 / CVSS v3 4.9 Attack vector: remote (network-reachable) / no user interaction Attack surface: `allowed_extensions` / `onload` / `MediaUploadController` / `FileSaver` 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
**Cross-site scripting (XSS)** (CWE-79) exists in shopware/core. Attackers reach the vulnerable code path via ``allowed_extensions`` without authentication.
📍 Affected scope
shopware/core — . Attack surface: `allowed_extensions` / `onload` / `MediaUploadController` / `FileSaver`.
🔥 Severity
Severity: Medium (CVSS 4.9/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 request patterns matching this CVE's known IOCs. Run `grep -r 'shopware/core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify
    grep -r 'shopware/core' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade shopware/core to 6.6.10.18

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

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

composer shopware/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]
composer 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"}]}]
Packagist shopware/platform
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.10.18"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →