How severe is GHSA-xvhc-gm7j-mhmc?

GHSA-xvhc-gm7j-mhmc has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xvhc-gm7j-mhmc?

GHSA-xvhc-gm7j-mhmc affects the following packages: shopware/core (Packagist), shopware/core (Packagist), shopware/platform (Packagist), shopware/platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xvhc-gm7j-mhmc?

Update shopware/core to 6.7.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvhc-gm7j-mhmc is resolved across your whole dependency graph.

How do I detect GHSA-xvhc-gm7j-mhmc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xvhc-gm7j-mhmc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xvhc-gm7j-mhmc?

O3 pinpoints whether GHSA-xvhc-gm7j-mhmc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xvhc-gm7j-mhmc actively exploited in the wild?

No public exploit code has been indexed for GHSA-xvhc-gm7j-mhmc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-xvhc-gm7j-mhmc?

GHSA-xvhc-gm7j-mhmc is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-xvhc-gm7j-mhmc published, and has it been updated?

GHSA-xvhc-gm7j-mhmc was published on June 4, 2026 and was last updated on June 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-xvhc-gm7j-mhmc

MEDIUM

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

Also known asCVE-2026-48015

Published

Jun 4, 2026

Updated

Jun 4, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐘shopware/core🐘shopware/core🐘shopware/platform🐘shopware/platform

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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:

Remove SVG from allowed_extensions if SVG upload is not a core requirement
Sanitize SVG content on upload using a library like enshrined/svg-sanitize (strips scripts, event handlers, external references)
Serve SVGs with Content-Disposition: attachment to prevent inline rendering
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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.10.1	6.7.10.1
🐘Packagist	`shopware/core`	all versions	6.6.10.18
🐘Packagist	`shopware/platform`	≥ 6.7.0.0&&< 6.7.10.1	6.7.10.1
🐘Packagist	`shopware/platform`	all versions	6.6.10.18

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopware/core to 6.7.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvhc-gm7j-mhmc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xvhc-gm7j-mhmc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xvhc-gm7j-mhmc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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: ```yaml allowed_extensions: ["jpg", "jpeg", "png", "webp", "avif", "gif", "svg", ...] ``` SVG is whitelisted. The upload path (`MediaUploadController` → `FileSaver` → `TypeDetector`) re

O3 Security · Impact-Aware SCA

Is GHSA-xvhc-gm7j-mhmc in your dependencies?

O3 detects GHSA-xvhc-gm7j-mhmc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works