<?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>Sun, 04 Oct 2026 19:16:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-255259</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-255259</link>
      <description>EUVD-2026-255259</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-255259</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53092</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53092</link>
      <description>&lt;p&gt;Strapi is an open source headless content management system. Strapi versions prior to 5.20.0 contain a CORS misconfiguration vulnerability in default installations. By default, Strapi reflects the value of the Origin header back in the Access-Control-Allow-Origin response header without proper validation or whitelisting. This allows an attacker-controlled site to send credentialed requests to the Strapi backend. An attacker can exploit this by hosting a malicious site on a different origin (e.g., different port) and sending requests with credentials to the Strapi API. The vulnerability is fixed in version 5.20.0. No known workarounds exist.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Strapi is an open source headless content management system. Strapi versions prior to 5.20.0 contain a CORS misconfiguration vulnerability in default installations. By default, Strapi reflects the value of the Origin header back in the Access-Control-Allow-Origin response header without proper validation or whitelisting. This allows an attacker-controlled site to send credentialed requests to the Strapi backend. An attacker can exploit this by hosting a malicious site on a different origin (e.g., different port) and sending requests with credentials to the Strapi API. The vulnerability is fixed in version 5.20.0. No known workarounds exist.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53092</guid>
    </item>
    <item>
      <title>GHSA-9329-mxxw-qwf8 — Strapi core vulnerable to sensitive data exposure via CORS misconfiguration</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9329-mxxw-qwf8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @strapi/core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A CORS misconfiguration vulnerability exists in default installations of Strapi where attacker-controlled origins are improperly reflected in API responses.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;By default, Strapi reflects the value of the Origin header back in the Access-Control-Allow-Origin response header without proper validation or whitelisting.&lt;/p&gt;
&lt;p&gt;Example:
`Origin: http://localhost:8888`
`Access-Control-Allow-Origin: http://localhost:8888`
`Access-Control-Allow-Credentials: true`&lt;/p&gt;
&lt;p&gt;This allows an attacker-controlled site (on a different port, like 8888) to send credentialed requests to the Strapi backend on 1337.&lt;/p&gt;
&lt;p&gt;### Suggested Fix&lt;/p&gt;
&lt;p&gt;1. Explicitly whitelist trusted origins
2. Avoid reflecting dynamic origins&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @strapi/core&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A CORS misconfiguration vulnerability exists in default installations of Strapi where attacker-controlled origins are improperly reflected in API responses.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;By default, Strapi reflects the value of the Origin header back in the Access-Control-Allow-Origin response header without proper validation or whitelisting.&lt;/p&gt;
&lt;p&gt;Example:
`Origin: http://localhost:8888`
`Access-Control-Allow-Origin: http://localhost:8888`
`Access-Control-Allow-Credentials: true`&lt;/p&gt;
&lt;p&gt;This allows an attacker-controlled site (on a different port, like 8888) to send credentialed requests to the Strapi backend on 1337.&lt;/p&gt;
&lt;p&gt;### Suggested Fix&lt;/p&gt;
&lt;p&gt;1. Explicitly whitelist trusted origins
2. Avoid reflecting dynamic origins&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9329-mxxw-qwf8</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2332 — Strapi: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2332</link>
      <description>&lt;p&gt;Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Strapi ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand zu verursachen und vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Strapi ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand zu verursachen und vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2332</guid>
    </item>
  </channel>
</rss>
