Advisory record · GHSA-xvhc-gm7j-mhmc

Shopware: Stored XSS via SVG file upload — no SVG sanitization

CVSS 4.9 MediumEPSS 0.0049 · 42nd percentile

Published by the GitHub Advisory Database at 4 Jun 2026, 19:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
shopware/corePackagist>=6.7.0.0, <6.7.10.1 || <6.6.10.186.7.10.1, 6.6.10.18
shopware/platformPackagist>=6.7.0.0, <6.7.10.1 || <6.6.10.186.7.10.1, 6.6.10.18
Identifiers
GHSA-xvhc-gm7j-mhmc · CVE-2026-48015 · PKSA-qf56-zbmm-29m8 · PKSA-xngt-2zh8-qhq6
Weakness (CWE)
CWE-79
Published
4 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Shopware's shopware/core and shopware/platform Packagist packages, in versions before 6.6.10.18 and from 6.7.0.0 up to but not including 6.7.10.1, allow SVG files through the media upload whitelist without sanitizing their contents. An admin user could upload an SVG containing JavaScript that then runs in the Shopware domain for anyone who views it, which the source says could lead to admin account takeover or customer data theft. Upgrade to shopware/core or shopware/platform 6.6.10.18 or 6.7.10.1, which are the listed fixed versions.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.9 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 42nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:57 UTC First seen by agentprime
  2. 31 Oct 2026, 13:57 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.