<?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>Tue, 06 Oct 2026 16:16:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292746</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292746</link>
      <description>EUVD-2026-292746</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292746</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41175</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41175</link>
      <description>&lt;p&gt;Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.20 and 6.13.0, manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts. The Control Panel requires authentication with minimal permissions in order to exploit. e.g. &amp;#34;view entries&amp;#34; permission to delete entries, or &amp;#34;view users&amp;#34; permission to delete users, etc. The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too. Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority. This has been fixed in 5.73.20 and 6.13.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.20 and 6.13.0, manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts. The Control Panel requires authentication with minimal permissions in order to exploit. e.g. &amp;#34;view entries&amp;#34; permission to delete entries, or &amp;#34;view users&amp;#34; permission to delete users, etc. The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too. Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority. This has been fixed in 5.73.20 and 6.13.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41175</guid>
    </item>
    <item>
      <title>GHSA-4jjr-vmv7-wh4w — Statamic: Unsafe method invocation via query value resolution allows data destruction</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4jjr-vmv7-wh4w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: statamic/cms&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts.&lt;/p&gt;
&lt;p&gt;The Control Panel requires authentication with minimal permissions in order to exploit. e.g. &amp;#34;view entries&amp;#34; permission to delete entries, or &amp;#34;view users&amp;#34; permission to delete users, etc.&lt;/p&gt;
&lt;p&gt;The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too.&lt;/p&gt;
&lt;p&gt;Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This has been fixed in 5.73.20 and 6.13.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: statamic/cms&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts.&lt;/p&gt;
&lt;p&gt;The Control Panel requires authentication with minimal permissions in order to exploit. e.g. &amp;#34;view entries&amp;#34; permission to delete entries, or &amp;#34;view users&amp;#34; permission to delete users, etc.&lt;/p&gt;
&lt;p&gt;The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too.&lt;/p&gt;
&lt;p&gt;Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This has been fixed in 5.73.20 and 6.13.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4jjr-vmv7-wh4w</guid>
    </item>
  </channel>
</rss>
