<?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>Wed, 14 Oct 2026 23:56:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-367800</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367800</link>
      <description>EUVD-2026-367800</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367800</guid>
    </item>
    <item>
      <title>fkie_cve-2026-68535</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-68535</link>
      <description>&lt;p&gt;Concrete CMS Area API&amp;#39;s block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller&amp;#39;s validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user&amp;#39;s file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file&amp;#39;s URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Concrete CMS Area API&amp;#39;s block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller&amp;#39;s validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user&amp;#39;s file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file&amp;#39;s URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-68535</guid>
    </item>
    <item>
      <title>GHSA-pcwm-p48j-jmfv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pcwm-p48j-jmfv</link>
      <description>&lt;p&gt;Concrete CMS Area API&amp;#39;s block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller&amp;#39;s validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user&amp;#39;s file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file&amp;#39;s URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Concrete CMS Area API&amp;#39;s block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller&amp;#39;s validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user&amp;#39;s file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file&amp;#39;s URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pcwm-p48j-jmfv</guid>
    </item>
  </channel>
</rss>
