<?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>Mon, 05 Oct 2026 20:45:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-275737</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275737</link>
      <description>EUVD-2026-275737</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275737</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27591</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27591</link>
      <description>&lt;p&gt;Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. Prior to 1.0.477, 1.1.12, and 1.2.12, Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in. To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access. This vulnerability is fixed in 1.0.477, 1.1.12, and 1.2.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. Prior to 1.0.477, 1.1.12, and 1.2.12, Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in. To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access. This vulnerability is fixed in 1.0.477, 1.1.12, and 1.2.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27591</guid>
    </item>
    <item>
      <title>GHSA-pgpf-m8m4-6cg6 — Winter vulnerable to privilege escalation by authenticated backend users</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pgpf-m8m4-6cg6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: winter/wn-backend-module&lt;/p&gt;
&lt;p&gt;## Impact
Affected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.&lt;/p&gt;
&lt;p&gt;To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.&lt;/p&gt;
&lt;p&gt;The Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles &amp;amp; permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).&lt;/p&gt;
&lt;p&gt;## Patches
Multiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.&lt;/p&gt;
&lt;p&gt;This security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.&lt;/p&gt;
&lt;p&gt;## Workarounds
If you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: winter/wn-backend-module&lt;/p&gt;
&lt;p&gt;## Impact
Affected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.&lt;/p&gt;
&lt;p&gt;To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.&lt;/p&gt;
&lt;p&gt;The Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles &amp;amp; permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).&lt;/p&gt;
&lt;p&gt;## Patches
Multiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.&lt;/p&gt;
&lt;p&gt;This security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.&lt;/p&gt;
&lt;p&gt;## Workarounds
If you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pgpf-m8m4-6cg6</guid>
    </item>
  </channel>
</rss>
