<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 08:05:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338576</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338576</link>
      <description>EUVD-2026-338576</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338576</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48015</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48015</link>
      <description>&lt;p&gt;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, &amp;lt;script&amp;gt;, and &amp;lt;foreignObject&amp;gt; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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, &amp;lt;script&amp;gt;, and &amp;lt;foreignObject&amp;gt; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-48015</guid>
    </item>
    <item>
      <title>GHSA-xvhc-gm7j-mhmc — Shopware: Stored XSS via SVG file upload — no SVG sanitization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xvhc-gm7j-mhmc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopware/core, Packagist: shopware/platform&lt;/p&gt;
&lt;p&gt;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`, `&amp;lt;script&amp;gt;`, `&amp;lt;foreignObject&amp;gt;`) executes in the context of the Shopware domain when accessed.&lt;/p&gt;
&lt;p&gt;## The Problem&lt;/p&gt;
&lt;p&gt;In `src/Core/Framework/Resources/config/packages/shopware.yaml`, line 194:&lt;/p&gt;
&lt;p&gt;```yaml
allowed_extensions: [&amp;#34;jpg&amp;#34;, &amp;#34;jpeg&amp;#34;, &amp;#34;png&amp;#34;, &amp;#34;webp&amp;#34;, &amp;#34;avif&amp;#34;, &amp;#34;gif&amp;#34;, &amp;#34;svg&amp;#34;, ...]
```&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A search of the entire codebase for SVG sanitization returns — no `DOMPurify`, no `svg-sanitize`, no `strip_tags` on SVG content, nothing.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Suggested Fix&lt;/p&gt;
&lt;p&gt;Either:&lt;/p&gt;
&lt;p&gt;1. **Remove SVG from `allowed_extensions`** if SVG upload is not a core requirement
2. **Sanitize SVG content** on upload using a library like `enshrined/svg-sanitize` (strips scripts, event handlers, external references)
3. **Serve SVGs with `Content-Disposition: attachment`** to prevent inline rendering
4. **Serve SVGs from a separate domain** (like Nextcloud&amp;#39;s `usercontent.apps.next…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopware/core, Packagist: shopware/platform&lt;/p&gt;
&lt;p&gt;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`, `&amp;lt;script&amp;gt;`, `&amp;lt;foreignObject&amp;gt;`) executes in the context of the Shopware domain when accessed.&lt;/p&gt;
&lt;p&gt;## The Problem&lt;/p&gt;
&lt;p&gt;In `src/Core/Framework/Resources/config/packages/shopware.yaml`, line 194:&lt;/p&gt;
&lt;p&gt;```yaml
allowed_extensions: [&amp;#34;jpg&amp;#34;, &amp;#34;jpeg&amp;#34;, &amp;#34;png&amp;#34;, &amp;#34;webp&amp;#34;, &amp;#34;avif&amp;#34;, &amp;#34;gif&amp;#34;, &amp;#34;svg&amp;#34;, ...]
```&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A search of the entire codebase for SVG sanitization returns — no `DOMPurify`, no `svg-sanitize`, no `strip_tags` on SVG content, nothing.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Suggested Fix&lt;/p&gt;
&lt;p&gt;Either:&lt;/p&gt;
&lt;p&gt;1. **Remove SVG from `allowed_extensions`** if SVG upload is not a core requirement
2. **Sanitize SVG content** on upload using a library like `enshrined/svg-sanitize` (strips scripts, event handlers, external references)
3. **Serve SVGs with `Content-Disposition: attachment`** to prevent inline rendering
4. **Serve SVGs from a separate domain** (like Nextcloud&amp;#39;s `usercontent.apps.next…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xvhc-gm7j-mhmc</guid>
    </item>
  </channel>
</rss>
