<?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-23T06:02:19.171626+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-205671</id>
    <title>EUVD-2026-205671</title>
    <updated>2026-10-23T06:02:19.219125+00:00</updated>
    <content>EUVD-2026-205671</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-205671"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-52600</id>
    <title>fkie_cve-2024-52600</title>
    <updated>2026-10-23T06:02:19.219161+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Statmatic is a Laravel and Git powered content management system (CMS). Prior to version 5.17.0, assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured. The issue affects front-end forms with `assets` fields and other places where assets can be uploaded, although users would need upload permissions anyway. Files can be uploaded so they would be located on the server in a different location, and potentially override existing files. Traversal outside an asset container is not possible. This path traversal vulnerability has been fixed in 5.17.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-52600"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-p7f6-8mcm-fwv3</id>
    <title>GHSA-p7f6-8mcm-fwv3 — Statamic CMS has a Path Traversal in Asset Upload</title>
    <updated>2026-10-23T06:02:19.219196+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: statamic/cms</p>
<p>Assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured.</p>
<p>### Impact</p>
<p>- Affects front-end forms with `assets` fields.
- Affects other places where assets can be uploaded, although users would need upload permissions anyway.
- Files can be uploaded so they would be located on the server in a different location, and potentially override existing files.
- Traversal _outside_ an asset container was not possible.</p>
<p>### Patches</p>
<p>This has been fixed in 5.17.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-p7f6-8mcm-fwv3"/>
  </entry>
</feed>
