<?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, 10 Oct 2026 12:35:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-217717</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-217717</link>
      <description>EUVD-2026-217717</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-217717</guid>
    </item>
    <item>
      <title>fkie_cve-2021-38346</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-38346</link>
      <description>&lt;p&gt;The Brizy Page Builder plugin &amp;lt;= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with &amp;#34;../&amp;#34; to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Brizy Page Builder plugin &amp;lt;= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with &amp;#34;../&amp;#34; to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-38346</guid>
    </item>
    <item>
      <title>GHSA-gq9p-f72g-3m6j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gq9p-f72g-3m6j</link>
      <description>&lt;p&gt;The Brizy Page Builder plugin &amp;lt;= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with &amp;#34;../&amp;#34; to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Brizy Page Builder plugin &amp;lt;= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with &amp;#34;../&amp;#34; to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gq9p-f72g-3m6j</guid>
    </item>
    <item>
      <title>gsd-2021-38346</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-38346</link>
      <description>gsd-2021-38346</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-38346</guid>
    </item>
  </channel>
</rss>
