<?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 06:31:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-358139</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358139</link>
      <description>EUVD-2026-358139</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358139</guid>
    </item>
    <item>
      <title>fkie_cve-2026-78391</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78391</link>
      <description>&lt;p&gt;RansomLook contains a stored cross-site scripting (XSS) vulnerability in the cryptocurrency wallet detail view. Cryptocurrency addresses and blockchain names originating from external sources, including the public crowd-sourced ransomwhe.re feed, were stored without sufficient validation and later embedded directly into an inline JavaScript onclick handler.&lt;/p&gt;
&lt;p&gt;Although Jinja HTML autoescaping was applied, it does not provide adequate protection when untrusted data is inserted into a JavaScript string inside an HTML attribute. HTML entities such as &amp;amp;#39; are decoded by the browser&amp;#39;s HTML parser before the resulting attribute is interpreted as JavaScript. Consequently, a specially crafted cryptocurrency address containing quote characters and JavaScript syntax could escape the intended string literal and execute arbitrary JavaScript when a user clicked the affected wallet&amp;#39;s CSV export button.&lt;/p&gt;
&lt;p&gt;Because cryptocurrency information imported from an untrusted upstream could reach the vulnerable rendering path, exploitation may not require an authenticated RansomLook account if an attacker can introduce a malicious wallet record into a consumed external data source. Successful exploitation could allow attacker-controlled JavaScript to execute in the security context of the RansomLook web application, potentially exposing information accessible to the victim or performing actions with the victim&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The patch mitigates the issue by validating cryptocurrency addresses and…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RansomLook contains a stored cross-site scripting (XSS) vulnerability in the cryptocurrency wallet detail view. Cryptocurrency addresses and blockchain names originating from external sources, including the public crowd-sourced ransomwhe.re feed, were stored without sufficient validation and later embedded directly into an inline JavaScript onclick handler.&lt;/p&gt;
&lt;p&gt;Although Jinja HTML autoescaping was applied, it does not provide adequate protection when untrusted data is inserted into a JavaScript string inside an HTML attribute. HTML entities such as &amp;amp;#39; are decoded by the browser&amp;#39;s HTML parser before the resulting attribute is interpreted as JavaScript. Consequently, a specially crafted cryptocurrency address containing quote characters and JavaScript syntax could escape the intended string literal and execute arbitrary JavaScript when a user clicked the affected wallet&amp;#39;s CSV export button.&lt;/p&gt;
&lt;p&gt;Because cryptocurrency information imported from an untrusted upstream could reach the vulnerable rendering path, exploitation may not require an authenticated RansomLook account if an attacker can introduce a malicious wallet record into a consumed external data source. Successful exploitation could allow attacker-controlled JavaScript to execute in the security context of the RansomLook web application, potentially exposing information accessible to the victim or performing actions with the victim&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The patch mitigates the issue by validating cryptocurrency addresses and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-78391</guid>
    </item>
    <item>
      <title>GHSA-mp5g-mcx2-r5xh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mp5g-mcx2-r5xh</link>
      <description>&lt;p&gt;RansomLook contains a stored cross-site scripting (XSS) vulnerability in the cryptocurrency wallet detail view. Cryptocurrency addresses and blockchain names originating from external sources, including the public crowd-sourced ransomwhe.re feed, were stored without sufficient validation and later embedded directly into an inline JavaScript onclick handler.&lt;/p&gt;
&lt;p&gt;Although Jinja HTML autoescaping was applied, it does not provide adequate protection when untrusted data is inserted into a JavaScript string inside an HTML attribute. HTML entities such as &amp;amp;#39; are decoded by the browser&amp;#39;s HTML parser before the resulting attribute is interpreted as JavaScript. Consequently, a specially crafted cryptocurrency address containing quote characters and JavaScript syntax could escape the intended string literal and execute arbitrary JavaScript when a user clicked the affected wallet&amp;#39;s CSV export button.&lt;/p&gt;
&lt;p&gt;Because cryptocurrency information imported from an untrusted upstream could reach the vulnerable rendering path, exploitation may not require an authenticated RansomLook account if an attacker can introduce a malicious wallet record into a consumed external data source. Successful exploitation could allow attacker-controlled JavaScript to execute in the security context of the RansomLook web application, potentially exposing information accessible to the victim or performing actions with the victim&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The patch mitigates the issue by validating cryptocurrency addresses and…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RansomLook contains a stored cross-site scripting (XSS) vulnerability in the cryptocurrency wallet detail view. Cryptocurrency addresses and blockchain names originating from external sources, including the public crowd-sourced ransomwhe.re feed, were stored without sufficient validation and later embedded directly into an inline JavaScript onclick handler.&lt;/p&gt;
&lt;p&gt;Although Jinja HTML autoescaping was applied, it does not provide adequate protection when untrusted data is inserted into a JavaScript string inside an HTML attribute. HTML entities such as &amp;amp;#39; are decoded by the browser&amp;#39;s HTML parser before the resulting attribute is interpreted as JavaScript. Consequently, a specially crafted cryptocurrency address containing quote characters and JavaScript syntax could escape the intended string literal and execute arbitrary JavaScript when a user clicked the affected wallet&amp;#39;s CSV export button.&lt;/p&gt;
&lt;p&gt;Because cryptocurrency information imported from an untrusted upstream could reach the vulnerable rendering path, exploitation may not require an authenticated RansomLook account if an attacker can introduce a malicious wallet record into a consumed external data source. Successful exploitation could allow attacker-controlled JavaScript to execute in the security context of the RansomLook web application, potentially exposing information accessible to the victim or performing actions with the victim&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The patch mitigates the issue by validating cryptocurrency addresses and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mp5g-mcx2-r5xh</guid>
    </item>
  </channel>
</rss>
