<?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>Thu, 22 Oct 2026 02:08:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-195690</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-195690</link>
      <description>EUVD-2026-195690</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-195690</guid>
    </item>
    <item>
      <title>fkie_cve-2023-38499</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38499</link>
      <description>&lt;p&gt;TYPO3 is an open source PHP based web content management system. Starting in version 9.4.0 and prior to versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, and 12.4.4, in multi-site scenarios, enumerating the HTTP query parameters `id` and `L` allowed out-of-scope access to rendered content in the website frontend. For instance, this allowed visitors to access content of an internal site by adding handcrafted query parameters to the URL of a site that was publicly available. TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 fix the problem.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;TYPO3 is an open source PHP based web content management system. Starting in version 9.4.0 and prior to versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, and 12.4.4, in multi-site scenarios, enumerating the HTTP query parameters `id` and `L` allowed out-of-scope access to rendered content in the website frontend. For instance, this allowed visitors to access content of an internal site by adding handcrafted query parameters to the URL of a site that was publicly available. TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 fix the problem.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-38499</guid>
    </item>
    <item>
      <title>GHSA-jq6g-4v5m-wm9r — Information Disclosure due to Out-of-scope Site Resolution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jq6g-4v5m-wm9r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core&lt;/p&gt;
&lt;p&gt;&amp;gt; ### CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (3.5)&lt;/p&gt;
&lt;p&gt;### Problem
In multi-site scenarios, enumerating the HTTP query parameters `id` and `L` allowed out-of-scope access to rendered content in the website frontend. For instance, this allowed visitors to access content of an internal site by adding handcrafted query parameters to the URL of a site that was publicly available.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 that fix the problem described above.&lt;/p&gt;
&lt;p&gt;&amp;gt; ℹ️ **Strong security defaults - Manual actions required**
&amp;gt; Resolving sites by the `id` and `L` HTTP query parameters is now denied per default. However, it is still allowed to resolve a particular page by e.g. `https://example.org/?id=123&amp;amp;L=0` - as long as the `page-id 123` is in the scope of the site configured for the `base-url example.org`.
&amp;gt; The new feature flag `security.frontend.allowInsecureSiteResolutionByQueryParameters` - which is disabled per default - can be used to reactivate the previous behavior.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to Garvin Hicking who reported this issue, and to TYPO3 core &amp;amp; security team members Oliver Hader and Benjamin Franzke who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2023-003](https://typo3.org/security/advisory/typo3-core-sa-2023-003)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core&lt;/p&gt;
&lt;p&gt;&amp;gt; ### CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C` (3.5)&lt;/p&gt;
&lt;p&gt;### Problem
In multi-site scenarios, enumerating the HTTP query parameters `id` and `L` allowed out-of-scope access to rendered content in the website frontend. For instance, this allowed visitors to access content of an internal site by adding handcrafted query parameters to the URL of a site that was publicly available.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 that fix the problem described above.&lt;/p&gt;
&lt;p&gt;&amp;gt; ℹ️ **Strong security defaults - Manual actions required**
&amp;gt; Resolving sites by the `id` and `L` HTTP query parameters is now denied per default. However, it is still allowed to resolve a particular page by e.g. `https://example.org/?id=123&amp;amp;L=0` - as long as the `page-id 123` is in the scope of the site configured for the `base-url example.org`.
&amp;gt; The new feature flag `security.frontend.allowInsecureSiteResolutionByQueryParameters` - which is disabled per default - can be used to reactivate the previous behavior.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to Garvin Hicking who reported this issue, and to TYPO3 core &amp;amp; security team members Oliver Hader and Benjamin Franzke who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2023-003](https://typo3.org/security/advisory/typo3-core-sa-2023-003)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jq6g-4v5m-wm9r</guid>
    </item>
    <item>
      <title>gsd-2023-38499</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-38499</link>
      <description>gsd-2023-38499</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-38499</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-1878 — TYPO3 Core: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1878</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen oder Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen oder Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1878</guid>
    </item>
  </channel>
</rss>
