<?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>Sun, 18 Oct 2026 05:21:12 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-94041</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-94041</link>
      <description>cnvd-2021-94041</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-94041</guid>
    </item>
    <item>
      <title>EUVD-2026-23222</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-23222</link>
      <description>EUVD-2026-23222</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-23222</guid>
    </item>
    <item>
      <title>fkie_cve-2021-22968</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-22968</link>
      <description>&lt;p&gt;A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below.The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it&amp;#39;s possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration.To fix this, a check for allowed file extensions was added before downloading files to a tmp directory.Concrete CMS Security Team gave this a CVSS v3.1 score of 5.4 AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:NThis fix is also in Concrete version 9.0.0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below.The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it&amp;#39;s possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration.To fix this, a check for allowed file extensions was added before downloading files to a tmp directory.Concrete CMS Security Team gave this a CVSS v3.1 score of 5.4 AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:NThis fix is also in Concrete version 9.0.0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-22968</guid>
    </item>
    <item>
      <title>GHSA-g3p2-hfqr-9m25 — Improper file handling in concrete5/core</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g3p2-hfqr-9m25</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: concrete5/core&lt;/p&gt;
&lt;p&gt;A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it&amp;#39;s possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: concrete5/core&lt;/p&gt;
&lt;p&gt;A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it&amp;#39;s possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g3p2-hfqr-9m25</guid>
    </item>
    <item>
      <title>gsd-2021-22968</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-22968</link>
      <description>gsd-2021-22968</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-22968</guid>
    </item>
  </channel>
</rss>
