<?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, 17 Nov 2026 15:56:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-125160 — TYPO3 CMS - Information Disclosure in Form Framework</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-125160</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; TYPO3 CMS&lt;/p&gt;
&lt;p&gt;Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system&amp;#39;s length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server&amp;#39;s temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form.&lt;/p&gt;
&lt;p&gt;If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; TYPO3 CMS&lt;/p&gt;
&lt;p&gt;Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system&amp;#39;s length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server&amp;#39;s temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form.&lt;/p&gt;
&lt;p&gt;If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-125160</guid>
    </item>
  </channel>
</rss>
