Shopware: Stored XSS via SVG file upload — no SVG sanitization
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.10.18, 6.7.10.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, SVG files are in the allowed_extensions whitelist in src/Core/Framework/Resources/config/packages/shopware.yaml and can be uploaded via the media manager without SVG content sanitization in the upload pipeline from MediaUploadController to FileSaver to TypeDetector, allowing malicious SVG JavaScript such as onload, <script>, and <foreignObject> to execute in the Shopware domain when the uploaded SVG is viewed. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- shopware shopware
fixed in 6.6.10.18; From 6.7.0.0 · fixed in 6.7.10.1
- shopware platform
fixed in 6.6.10.18; From 6.7.0.0 · fixed in 6.7.10.1
- shopware/corePackagist
From 6.7.0.0 · fixed in 6.7.10.1
- shopware/corePackagist
fixed in 6.6.10.18
- shopware/platformPackagist
From 6.7.0.0 · fixed in 6.7.10.1
- shopware/platformPackagist
fixed in 6.6.10.18