<?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>Fri, 23 Oct 2026 06:01:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-23607</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-23607</link>
      <description>EUVD-2026-23607</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-23607</guid>
    </item>
    <item>
      <title>fkie_cve-2021-24171</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-24171</link>
      <description>&lt;p&gt;The WooCommerce Upload Files WordPress plugin before 59.4 ran a single sanitization pass to remove blocked extensions such as .php. It was possible to bypass this and upload a file with a PHP extension by embedding a &amp;#34;blocked&amp;#34; extension within another &amp;#34;blocked&amp;#34; extension in the &amp;#34;wcuf_file_name&amp;#34; parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the &amp;#34;wcuf_current_upload_session_id&amp;#34; parameter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WooCommerce Upload Files WordPress plugin before 59.4 ran a single sanitization pass to remove blocked extensions such as .php. It was possible to bypass this and upload a file with a PHP extension by embedding a &amp;#34;blocked&amp;#34; extension within another &amp;#34;blocked&amp;#34; extension in the &amp;#34;wcuf_file_name&amp;#34; parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the &amp;#34;wcuf_current_upload_session_id&amp;#34; parameter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-24171</guid>
    </item>
    <item>
      <title>GHSA-73q3-2843-4j2x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-73q3-2843-4j2x</link>
      <description>&lt;p&gt;The WooCommerce Upload Files WordPress plugin before 59.4 ran a single sanitization pass to remove blocked extensions such as .php. It was possible to bypass this and upload a file with a PHP extension by embedding a &amp;#34;blocked&amp;#34; extension within another &amp;#34;blocked&amp;#34; extension in the &amp;#34;wcuf_file_name&amp;#34; parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the &amp;#34;wcuf_current_upload_session_id&amp;#34; parameter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WooCommerce Upload Files WordPress plugin before 59.4 ran a single sanitization pass to remove blocked extensions such as .php. It was possible to bypass this and upload a file with a PHP extension by embedding a &amp;#34;blocked&amp;#34; extension within another &amp;#34;blocked&amp;#34; extension in the &amp;#34;wcuf_file_name&amp;#34; parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the &amp;#34;wcuf_current_upload_session_id&amp;#34; parameter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-73q3-2843-4j2x</guid>
    </item>
    <item>
      <title>gsd-2021-24171</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-24171</link>
      <description>gsd-2021-24171</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-24171</guid>
    </item>
  </channel>
</rss>
