<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T18:07:07.285795+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-328885</id>
    <title>EUVD-2026-328885</title>
    <updated>2026-10-06T18:07:07.340885+00:00</updated>
    <content>EUVD-2026-328885</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-328885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49287</id>
    <title>fkie_cve-2026-49287</title>
    <updated>2026-10-06T18:07:07.340925+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.23 and 6.20.0, the fix for CVE-2026-41175 was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets. This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value. This has been fixed in 5.73.23 and 6.20.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-49287"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-m92m-r54r-x8r2</id>
    <title>GHSA-m92m-r54r-x8r2 — Statamic CMS's unsafe method invocation via collection sorting allows data destruction</title>
    <updated>2026-10-06T18:07:07.340965+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: statamic/cms</p>
<p>### Impact</p>
<p>The fix for GHSA-4jjr-vmv7-wh4w was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets.</p>
<p>This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value.</p>
<p>### Patches</p>
<p>This has been fixed in 5.73.23 and 6.20.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-m92m-r54r-x8r2"/>
  </entry>
</feed>
