<?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>Sat, 03 Oct 2026 04:08:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-197899</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-197899</link>
      <description>EUVD-2026-197899</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-197899</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47882</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47882</link>
      <description>&lt;p&gt;OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47882</guid>
    </item>
    <item>
      <title>GHSA-j8hp-f2mj-586g — OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j8hp-f2mj-586g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.openrefine:openrefine&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message.&lt;/p&gt;
&lt;p&gt;It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, as in GHSA-m88m-crr9-jvqq, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The `Command.respondWithErrorPage` (through `HttpUtilities.respondWithErrorPage`) function renders the Velocity template `error.vt`, which contains the `$message` and `$stack` variables, which are included in the response as-is:&lt;/p&gt;
&lt;p&gt;https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/error.vt#L52-L53&lt;/p&gt;
&lt;p&gt;However, the message can contain HTML tags, which would then be interpreted by the browser. A mitigation would be to escape both the message and stack trace, perhaps using Guava&amp;#39;s HTML escaper.&lt;/p&gt;
&lt;p&gt;Flows that report errors as `application/json` responses are not interpreted by the browser and so not affected by this issue.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;In OpenRefine, use the &amp;#34;Import project&amp;#34; feature to import the following URL (or upload it as a file): https://wandernauta.nl/oa/example.tar.gz&lt;/p&gt;
&lt;p&gt;A JavaScript alert appears.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Execution of arbitrary JavaScript in the victim&amp;#39;s browser, provided the victim can be convinced to imp…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.openrefine:openrefine&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message.&lt;/p&gt;
&lt;p&gt;It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, as in GHSA-m88m-crr9-jvqq, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The `Command.respondWithErrorPage` (through `HttpUtilities.respondWithErrorPage`) function renders the Velocity template `error.vt`, which contains the `$message` and `$stack` variables, which are included in the response as-is:&lt;/p&gt;
&lt;p&gt;https://github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/error.vt#L52-L53&lt;/p&gt;
&lt;p&gt;However, the message can contain HTML tags, which would then be interpreted by the browser. A mitigation would be to escape both the message and stack trace, perhaps using Guava&amp;#39;s HTML escaper.&lt;/p&gt;
&lt;p&gt;Flows that report errors as `application/json` responses are not interpreted by the browser and so not affected by this issue.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;In OpenRefine, use the &amp;#34;Import project&amp;#34; feature to import the following URL (or upload it as a file): https://wandernauta.nl/oa/example.tar.gz&lt;/p&gt;
&lt;p&gt;A JavaScript alert appears.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Execution of arbitrary JavaScript in the victim&amp;#39;s browser, provided the victim can be convinced to imp…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j8hp-f2mj-586g</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47882</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47882</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:22.04:LTS: openrefine, Ubuntu:Pro:24.04:LTS: openrefine&lt;/p&gt;
&lt;p&gt;OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:22.04:LTS: openrefine, Ubuntu:Pro:24.04:LTS: openrefine&lt;/p&gt;
&lt;p&gt;OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in &amp;#34;Something went wrong!&amp;#34; error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult.  However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47882</guid>
    </item>
  </channel>
</rss>
