ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-48015

Stored XSS via SVG file upload — no SVG sanitization

Published May 19, 2026 · catalog updated May 20, 2026 · Stored XSS via SVG

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-48015. EPSS is 0.48%. Act only if a listed version of Stored XSS via SVG is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Stored XSS via SVG).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.48%
Remediation
Version ranges on file
Affected products
composer shopware/core · composer shopware/platform

Hi Shopware Security Team, SVG files are in the 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 ( , , ) executes in the context of the Shopware domain when accessed. ## The Problem In , line 194: SVG is whitelisted. The upload path ( → → ) recognizes SVG as with flag, but no code strips JavaScript, event handlers, or external entity references from the SVG XML. I searched the entire codebase for SVG sanitization — no , no , no on SVG content, nothing. ## Impact 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. ## Suggested Fix Either: 1. **Remove SVG from ** if SVG upload is not a core requirement 2. **Sanitize SVG content** on upload using a library like (strips scripts, event handlers, external references) 3. **Serve SVGs with ** to prevent inline rendering 4. **Serve SVGs from a separate domain** (like Nextcloud's ) Option 2 is the most practical — is already used by WordPress and other PHP projects. Regards & BG, Keyvan Hardani

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer shopware/core<6.6.10.18
  • composer shopware/core>=6.7.0.0 <6.7.10.1
  • composer shopware/platform<6.6.10.18
  • composer shopware/platform>=6.7.0.0 <6.7.10.1

How to fix CVE-2026-48015

  • Upgrade

    CVE-2026-48015 lists a fix boundary at 6.6.10.18. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <6.6.10.18

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-48015. EPSS is 0.48%. Act only if a listed version of Stored XSS via SVG is installed.

Which versions are affected?

Compare what you have installed with <6.6.10.18, >=6.7.0.0 <6.7.10.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-79: Cross-site Scripting (XSS). EPSS 0.48%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Shopware securityWordPress security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 19, 2026 · Maintainer security tabs

    Detected

    Hi Shopware Security Team, SVG files are in the 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 ( , , ) executes in the context of the Shopware domain when accessed. ## The Problem In , line 194: SVG is whitelisted. The upload path ( → → ) recognizes SVG as with flag, but

  2. May 20, 2026 · Maintainer security tabs

    Updated

    Hi Shopware Security Team, SVG files are in the 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 ( , , ) executes in the context of the Shopware domain when accessed. ## The Problem In , line 194: SVG is whitelisted. The upload path ( → → ) recognizes SVG as with flag, but

Sources

  • CVE.orgVulnerability recordCVE-2026-48015

    Official CVE identifier

    cve.org
  • Maintainer security tabsVendor advisoryGHSA-xvhc-gm7j-mhmc

    Hi Shopware Security Team, SVG files are in the 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 ( , , ) executes in the context of the Shopware domain when accessed. ## The Problem In , line 194: SVG is whitelisted. The upload path ( → → ) recognizes SVG as with flag, but

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 2, 2026
  • Maintainer security tabsNov 2, 2026