<?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>Mon, 05 Oct 2026 06:19:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-319649</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319649</link>
      <description>EUVD-2026-319649</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319649</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33741</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33741</link>
      <description>&lt;p&gt;EspoCRM is an open source customer relationship management application. Versions 9.3.3 and below allow authenticated users to upload SVG attachments through normal attachment-capable fields and later serve those SVG files as top-level inline documents through both the attachment and image entry points, resulting in stored cross-user XSS reachable through a normal attachment workflow. Although inline SVG script is blocked by the response CSP, the same CSP still allows same-origin external script. As a result, an attacker can upload a malicious SVG together with a second attacker-controlled JavaScript attachment, then trick another user into opening the SVG to execute JavaScript in the victim&amp;#39;s EspoCRM origin. This issue has been fixed in version 9.3.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;EspoCRM is an open source customer relationship management application. Versions 9.3.3 and below allow authenticated users to upload SVG attachments through normal attachment-capable fields and later serve those SVG files as top-level inline documents through both the attachment and image entry points, resulting in stored cross-user XSS reachable through a normal attachment workflow. Although inline SVG script is blocked by the response CSP, the same CSP still allows same-origin external script. As a result, an attacker can upload a malicious SVG together with a second attacker-controlled JavaScript attachment, then trick another user into opening the SVG to execute JavaScript in the victim&amp;#39;s EspoCRM origin. This issue has been fixed in version 9.3.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33741</guid>
    </item>
  </channel>
</rss>
