<?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>Sat, 03 Oct 2026 18:44:52 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0722 — De multiples vulnérabilités ont été découvertes dans Typo3. Certaines d'entre elles permettent à un attaquant de provoq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0722</link>
      <description>certfr-2026-avi-0722</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0722</guid>
    </item>
    <item>
      <title>EUVD-2026-337864</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337864</link>
      <description>EUVD-2026-337864</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337864</guid>
    </item>
    <item>
      <title>fkie_cve-2026-11607</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-11607</link>
      <description>&lt;p&gt;Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-11607</guid>
    </item>
    <item>
      <title>GHSA-pjpj-v387-x4vq — TYPO3 CMS has Broken Access Control in its Form Framework</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pjpj-v387-x4vq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core, Packagist: typo3/cms-form&lt;/p&gt;
&lt;p&gt;### Problem
Backend users with access to the Form Framework were able to use files not ending in `.form.yaml` as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
TYPO3 CMS thanks “Ethan” for reporting this issue, and TYPO3 core &amp;amp; security team member Oliver Hader for fixing it.&lt;/p&gt;
&lt;p&gt;### Resources
* [TYPO3-CORE-SA-2026-019](https://typo3.org/security/advisory/typo3-core-sa-2026-019)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core, Packagist: typo3/cms-form&lt;/p&gt;
&lt;p&gt;### Problem
Backend users with access to the Form Framework were able to use files not ending in `.form.yaml` as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
TYPO3 CMS thanks “Ethan” for reporting this issue, and TYPO3 core &amp;amp; security team member Oliver Hader for fixing it.&lt;/p&gt;
&lt;p&gt;### Resources
* [TYPO3-CORE-SA-2026-019](https://typo3.org/security/advisory/typo3-core-sa-2026-019)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pjpj-v387-x4vq</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1835 — TYPO3 Core: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1835</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um Sicherheitsbeschränkungen zu umgehen, Benutzer auf schädliche Websites umzuleiten, beliebigen Code auszuführen, Berechtigungen zu eskalieren oder andere Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um Sicherheitsbeschränkungen zu umgehen, Benutzer auf schädliche Websites umzuleiten, beliebigen Code auszuführen, Berechtigungen zu eskalieren oder andere Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1835</guid>
    </item>
  </channel>
</rss>
