<?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, 07 Oct 2026 12:22:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32752 — FreeScout: Broken Access Control in ThreadPolicy — Any User Can Read/Edit All Customer Messages</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32752</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; freescout-help-desk freescout&lt;/p&gt;
&lt;p&gt;FreeScout is a free help desk and shared inbox built with PHP&amp;#39;s Laravel framework. In versions 1.8.208 and below, the ThreadPolicy::edit() method contains a broken access control vulnerability that allows any authenticated user (regardless of role or mailbox access) to read and modify all customer-created thread messages across all mailboxes. This flaw enables silent modification of customer messages (evidence tampering), bypasses the entire mailbox permission model, and constitutes a GDPR/compliance violation. The issue has been fixed in version 1.8.209.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; freescout-help-desk freescout&lt;/p&gt;
&lt;p&gt;FreeScout is a free help desk and shared inbox built with PHP&amp;#39;s Laravel framework. In versions 1.8.208 and below, the ThreadPolicy::edit() method contains a broken access control vulnerability that allows any authenticated user (regardless of role or mailbox access) to read and modify all customer-created thread messages across all mailboxes. This flaw enables silent modification of customer messages (evidence tampering), bypasses the entire mailbox permission model, and constitutes a GDPR/compliance violation. The issue has been fixed in version 1.8.209.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32752</guid>
    </item>
  </channel>
</rss>
