<?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>Mon, 12 Oct 2026 21:05:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-29003 — SvelteKit has Insufficient Cross-Site Request Forgery Protection</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-29003</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sveltejs kit&lt;/p&gt;
&lt;p&gt;SvelteKit is a web development framework. The SvelteKit framework offers developers an option to create simple REST APIs. This is done by defining a `+server.js` file, containing endpoint handlers for different HTTP methods.&lt;/p&gt;
&lt;p&gt;SvelteKit provides out-of-the-box cross-site request forgery (CSRF) protection to its users. While the implementation does a sufficient job in mitigating common CSRF attacks, prior to version 1.15.1, the protection can be bypassed by simply specifying a different `Content-Type` header value.&lt;/p&gt;
&lt;p&gt;If abused, this issue will allow malicious requests to be submitted from third-party domains, which can allow execution of operations within the context of the victim&amp;#39;s session, and in extreme scenarios can lead to unauthorized access to users’ accounts.&lt;/p&gt;
&lt;p&gt;SvelteKit 1.15.1 updates the `is_form_content_type` function call in the CSRF protection logic to include `text/plain`. As additional hardening of the CSRF protection mechanism against potential method overrides, SvelteKit 1.15.1 is now performing validation on `PUT`, `PATCH` and `DELETE` methods as well. This latter hardening is only needed to protect users who have put in some sort of `?_method= override` feature themselves in their `handle` hook, so that the request that resolve sees could be `PUT`/`PATCH`/`DELETE` when the browser issues a `POST` request.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sveltejs kit&lt;/p&gt;
&lt;p&gt;SvelteKit is a web development framework. The SvelteKit framework offers developers an option to create simple REST APIs. This is done by defining a `+server.js` file, containing endpoint handlers for different HTTP methods.&lt;/p&gt;
&lt;p&gt;SvelteKit provides out-of-the-box cross-site request forgery (CSRF) protection to its users. While the implementation does a sufficient job in mitigating common CSRF attacks, prior to version 1.15.1, the protection can be bypassed by simply specifying a different `Content-Type` header value.&lt;/p&gt;
&lt;p&gt;If abused, this issue will allow malicious requests to be submitted from third-party domains, which can allow execution of operations within the context of the victim&amp;#39;s session, and in extreme scenarios can lead to unauthorized access to users’ accounts.&lt;/p&gt;
&lt;p&gt;SvelteKit 1.15.1 updates the `is_form_content_type` function call in the CSRF protection logic to include `text/plain`. As additional hardening of the CSRF protection mechanism against potential method overrides, SvelteKit 1.15.1 is now performing validation on `PUT`, `PATCH` and `DELETE` methods as well. This latter hardening is only needed to protect users who have put in some sort of `?_method= override` feature themselves in their `handle` hook, so that the request that resolve sees could be `PUT`/`PATCH`/`DELETE` when the browser issues a `POST` request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-29003</guid>
    </item>
  </channel>
</rss>
