<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 08:40:41 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-68527</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-68527</link>
      <description>&lt;p&gt;Concrete CMS versions 8.3.0 through 9.5.2 are vulnerable to an authorization bypass in the Calendar event edit dialog (concrete/controllers/dialog/event/edit.php). The dialog checked permissions against the calendar identifier supplied in the request rather than the calendar owning the targeted event occurrence. A user with the &amp;#34;Add Event&amp;#34; permission on a single calendar could read and overwrite events on calendars they were not permitted to access, and could delete an event&amp;#39;s original local occurrence. Publishing the injected version to the live calendar, which demotes the previously approved version, additionally required the actor&amp;#39;s approve_calendar_event workflow rights or an auto-approving workflow. The Concrete CMS Security Team gave this a rank of 5.9 with CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Concrete CMS versions 8.3.0 through 9.5.2 are vulnerable to an authorization bypass in the Calendar event edit dialog (concrete/controllers/dialog/event/edit.php). The dialog checked permissions against the calendar identifier supplied in the request rather than the calendar owning the targeted event occurrence. A user with the &amp;#34;Add Event&amp;#34; permission on a single calendar could read and overwrite events on calendars they were not permitted to access, and could delete an event&amp;#39;s original local occurrence. Publishing the injected version to the live calendar, which demotes the previously approved version, additionally required the actor&amp;#39;s approve_calendar_event workflow rights or an auto-approving workflow. The Concrete CMS Security Team gave this a rank of 5.9 with CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-68527</guid>
    </item>
    <item>
      <title>GHSA-xgrc-pc59-m8cp</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-xgrc-pc59-m8cp</link>
      <description>&lt;p&gt;Concrete CMS versions 8.3.0 through 9.5.2 are vulnerable to an authorization bypass in the Calendar event edit dialog (concrete/controllers/dialog/event/edit.php). The dialog checked permissions against the calendar identifier supplied in the request rather than the calendar owning the targeted event occurrence. A user with the &amp;#34;Add Event&amp;#34; permission on a single calendar could read and overwrite events on calendars they were not permitted to access, and could delete an event&amp;#39;s original local occurrence. Publishing the injected version to the live calendar, which demotes the previously approved version, additionally required the actor&amp;#39;s approve_calendar_event workflow rights or an auto-approving workflow. The Concrete CMS Security Team gave this a rank of 5.9 with CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Concrete CMS versions 8.3.0 through 9.5.2 are vulnerable to an authorization bypass in the Calendar event edit dialog (concrete/controllers/dialog/event/edit.php). The dialog checked permissions against the calendar identifier supplied in the request rather than the calendar owning the targeted event occurrence. A user with the &amp;#34;Add Event&amp;#34; permission on a single calendar could read and overwrite events on calendars they were not permitted to access, and could delete an event&amp;#39;s original local occurrence. Publishing the injected version to the live calendar, which demotes the previously approved version, additionally required the actor&amp;#39;s approve_calendar_event workflow rights or an auto-approving workflow. The Concrete CMS Security Team gave this a rank of 5.9 with CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-xgrc-pc59-m8cp</guid>
    </item>
  </channel>
</rss>
