<?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>Thu, 08 Oct 2026 15:53:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8428 — CSRF token is not validated in the core CMS update controller for Concrete CMS 9.5.0 and below</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8428</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Concrete CMS&lt;/p&gt;
&lt;p&gt;Concrete CMS 9.5.0 and below emits a CSRF token in the local_available_update.php view ($token-&amp;gt;output(&amp;#39;do_update&amp;#39;)) but the corresponding do_update() method in concrete/controllers/single_page/dashboard/system/update/update.php never calls $this-&amp;gt;token-&amp;gt;validate(&amp;#39;do_update&amp;#39;). The form is rendered as a POST form, meaning the token reaches the browser, but because the controller discards it without verification, an attacker can craft a cross-site POST that triggers a core CMS update to an attacker-specified version string.  In order to be vulnerable, theictim must be passing canUpgrade()anda valid update version must be present under DIR_CORE_UPDATES. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.5 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks https://github.com/maru1009 for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Concrete CMS&lt;/p&gt;
&lt;p&gt;Concrete CMS 9.5.0 and below emits a CSRF token in the local_available_update.php view ($token-&amp;gt;output(&amp;#39;do_update&amp;#39;)) but the corresponding do_update() method in concrete/controllers/single_page/dashboard/system/update/update.php never calls $this-&amp;gt;token-&amp;gt;validate(&amp;#39;do_update&amp;#39;). The form is rendered as a POST form, meaning the token reaches the browser, but because the controller discards it without verification, an attacker can craft a cross-site POST that triggers a core CMS update to an attacker-specified version string.  In order to be vulnerable, theictim must be passing canUpgrade()anda valid update version must be present under DIR_CORE_UPDATES. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.5 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks https://github.com/maru1009 for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8428</guid>
    </item>
  </channel>
</rss>
