shopware/core
Affected
- introduced
6.7.0.0, fixed6.7.10.1(ecosystem)
Fixed versions
6.7.10.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-48015
Shopware: Stored XSS via SVG file upload — no SVG sanitization
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.
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:
enshrined/svg-sanitize (strips scripts, event handlers, external references)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
Medium Basis: The source's own band: MODERATE
6.7.0.0, fixed 6.7.10.1 (ecosystem)6.7.10.1
The export has no generic command for this ecosystem.
0, fixed 6.6.10.18 (ecosystem)6.6.10.18
The export has no generic command for this ecosystem.
6.7.0.0, fixed 6.7.10.1 (ecosystem)6.7.10.1
The export has no generic command for this ecosystem.
0, fixed 6.6.10.18 (ecosystem)6.6.10.18
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0