CVE-2026-48015

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
4.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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, `, ) 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 (MediaUploadControllerFileSaverTypeDetector) 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

CVSS v3
4.9
EG Score
4.9(low)
EPSS
12.0%
KEV
Not listed

Published

June 4, 2026

Last Modified

June 4, 2026

Vendor Advisories for CVE-2026-48015(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
shopware/core6.3.0.0 ... v6.6.9.0 (166 versions)6.6.10.18
shopware/platform6.3.0.0 ... v6.6.9.0 (166 versions)6.6.10.18

Data Freshness Timeline

(refreshed 4× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 11:49 UTCEG score recompute
  2. 2026-07-09 07:11 UTCEG score recompute
  3. 2026-07-08 09:34 UTCEG score recompute
  4. 2026-07-06 02:19 UTCEG score recompute
  5. 2026-07-03 03:27 UTCEG score recompute
  6. 2026-07-02 05:32 UTCEG score recompute
  7. 2026-07-01 07:55 UTCEG score recompute
  8. 2026-06-30 08:56 UTCEG score recompute
  9. 2026-06-29 10:58 UTCEG score recompute
  10. 2026-06-28 13:19 UTCEG score recompute
  11. 2026-06-27 15:38 UTCEG score recompute
  12. 2026-06-26 18:01 UTCEG score recompute
  13. 2026-06-25 20:22 UTCEG score recompute
  14. 2026-06-24 22:44 UTCEG score recompute
  15. 2026-06-24 01:07 UTCEG score recompute
  16. 2026-06-23 01:54 UTCEG score recompute
  17. 2026-06-19 19:47 UTCEG score recompute
  18. 2026-06-18 09:50 UTCEG score recompute
  19. 2026-06-17 11:55 UTCEG score recompute
  20. 2026-06-16 14:19 UTCEG score recompute
  21. 2026-06-15 15:50 UTCEG score recompute
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-14 18:13 UTCEG score recompute
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 20:22 UTCEG score recompute
Show 11 more
  1. 2026-06-12 23:12 UTCEPSS rescore
  2. 2026-06-12 22:44 UTCEG score recompute
  3. 2026-06-12 01:08 UTCEG score recompute
  4. 2026-06-11 03:30 UTCEG score recompute
  5. 2026-06-10 05:54 UTCEG score recompute
  6. 2026-06-09 08:17 UTCEG score recompute
  7. 2026-06-08 10:39 UTCEG score recompute
  8. 2026-06-07 13:01 UTCEG score recompute
  9. 2026-06-06 15:24 UTCEG score recompute
  10. 2026-06-05 17:47 UTCEG score recompute
  11. 2026-06-04 20:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48015?
CVE-2026-48015 is a medium vulnerability published on June 4, 2026. 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>,…
When was CVE-2026-48015 disclosed?
CVE-2026-48015 was first published in the National Vulnerability Database on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48015 actively exploited?
CVE-2026-48015 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48015?
CVE-2026-48015 has a CVSS v4.0 base score of 4.9 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48015?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48015, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48015

Explore →

Is Your Infrastructure Affected by CVE-2026-48015?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.