<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-23T06:01:09.335495+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-23607</id>
    <title>EUVD-2026-23607</title>
    <updated>2026-10-23T06:01:09.403339+00:00</updated>
    <content>EUVD-2026-23607</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-23607"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-24171</id>
    <title>fkie_cve-2021-24171</title>
    <updated>2026-10-23T06:01:09.403376+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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 "blocked" extension within another "blocked" extension in the "wcuf_file_name" parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the "wcuf_current_upload_session_id" parameter.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-24171"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-73q3-2843-4j2x</id>
    <title>GHSA-73q3-2843-4j2x</title>
    <updated>2026-10-23T06:01:09.403412+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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 "blocked" extension within another "blocked" extension in the "wcuf_file_name" parameter. It was also possible to perform a double extension attack and upload files to a different location via path traversal using the "wcuf_current_upload_session_id" parameter.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-73q3-2843-4j2x"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-24171</id>
    <title>gsd-2021-24171</title>
    <updated>2026-10-23T06:01:09.403432+00:00</updated>
    <content>gsd-2021-24171</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-24171"/>
  </entry>
</feed>
