CVE-2026-48015

SVG files are in the allowed_extensions whitelist and can be uploaded by any admin user via the media manager. There is zero SVG content sanitization anywhere in the upload pipeline. A malicious SVG with JavaScript (onload, <script>, <foreignObject>) executes in the context of the Shopware domain when accessed.

The Problem

In src/Core/Framework/Resources/config/packages/shopware.yaml, line 194:

allowed_extensions: ["jpg", "jpeg", "png", "webp", "avif", "gif", "svg", ...]

SVG is whitelisted. The upload path (MediaUploadController → FileSaver → TypeDetector) recognizes SVG as ImageType with VECTOR_GRAPHIC flag, but no code strips JavaScript, event handlers, or external entity references from the SVG XML.

A search of the entire codebase for SVG sanitization returns, no DOMPurify, no svg-sanitize, no strip_tags on SVG content, nothing.

Stored XSS affecting all users who view the uploaded SVG. In an e-commerce context, this can lead to admin account takeover, customer data theft, or malicious plugin installation.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-48015 has a CVSS score of 4.9 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.7.10.1, 6.6.10.18); upgrading removes the vulnerable code path.

Kodem intelligence

Either:

1. Remove SVG from allowed_extensions if SVG upload is not a core requirement
2. Sanitize SVG content on upload using a library like enshrined/svg-sanitize (strips scripts, event handlers, external references)
3. Serve SVGs with Content-Disposition: attachment to prevent inline rendering
4. Serve SVGs from a separate domain (like Nextcloud's usercontent.apps.nextcloud.com)

Option 2 is the most practical, enshrined/svg-sanitize is already used by WordPress and other PHP projects.

Regards & BG,
Keyvan Hardani

1. What is CVE-2026-48015? CVE-2026-48015 is a medium-severity cross-site scripting (XSS) vulnerability in shopware/core (composer), affecting versions >= 6.7.0.0, < 6.7.10.1. It is fixed in 6.7.10.1, 6.6.10.18. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-48015? CVE-2026-48015 has a CVSS score of 4.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-48015?
   • shopware/core (composer) (versions >= 6.7.0.0, < 6.7.10.1)
   • shopware/platform (composer) (versions >= 6.7.0.0, < 6.7.10.1)
4. Is there a fix for CVE-2026-48015? Yes. CVE-2026-48015 is fixed in 6.7.10.1, 6.6.10.18. Upgrade to this version or later.
5. Is CVE-2026-48015 exploitable, and should I be worried? Whether CVE-2026-48015 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-48015 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-48015?
   • Upgrade shopware/core to 6.7.10.1 or later
   • Upgrade shopware/core to 6.6.10.18 or later
   • Upgrade shopware/platform to 6.7.10.1 or later
   • Upgrade shopware/platform to 6.6.10.18 or later

Other vulnerabilities in shopware/core