<?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, 08 Oct 2026 05:53:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-362998</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362998</link>
      <description>EUVD-2026-362998</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362998</guid>
    </item>
    <item>
      <title>fkie_cve-2026-29113</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-29113</link>
      <description>&lt;p&gt;Craft is a content management system (CMS). Prior to 4.17.3 and 5.9.7, Craft CMS has a CSRF issue in the preview token endpoint at /actions/preview/create-token. The endpoint accepts an attacker-supplied previewToken. Because the action does not require POST and does not enforce a CSRF token, an attacker can force a logged-in victim editor to mint a preview token chosen by the attacker. That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope. This vulnerability is fixed in 4.17.3 and 5.9.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft is a content management system (CMS). Prior to 4.17.3 and 5.9.7, Craft CMS has a CSRF issue in the preview token endpoint at /actions/preview/create-token. The endpoint accepts an attacker-supplied previewToken. Because the action does not require POST and does not enforce a CSRF token, an attacker can force a logged-in victim editor to mint a preview token chosen by the attacker. That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope. This vulnerability is fixed in 4.17.3 and 5.9.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-29113</guid>
    </item>
    <item>
      <title>GHSA-vg3j-hpm9-8v5v — Craft CMS has a potential information disclosure vulnerability in preview tokens</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vg3j-hpm9-8v5v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Craft CMS has a CSRF issue in the preview token endpoint at `/actions/preview/create-token`.  The endpoint accepts an attacker-supplied `previewToken`.&lt;/p&gt;
&lt;p&gt;Because the action does not require POST and does not enforce a CSRF token, an attacker can force a logged-in victim editor to mint a preview token chosen by the attacker.&lt;/p&gt;
&lt;p&gt;That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Preconditions
- Victim is logged in to Craft control panel.
- Victim has active preview authorization in session for target content (e.g., opened/edited an entry).
- The attacker must know the target’s `canonicalId` and public URL path of that entry.&lt;/p&gt;
&lt;p&gt;## 1) Attacker prepares a fixed token
Use any 32-character value, for example:
```text
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
```&lt;/p&gt;
&lt;p&gt;## 2) CSRF victim into minting that token
Send the victim a link (or top-level redirect) such as:
```text
https://TARGET/actions/preview/create-token?elementType=craft%5Celements%5CEntry&amp;amp;canonicalId=123&amp;amp;siteId=1&amp;amp;previewToken=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&amp;amp;redirect=https%3A%2F%2FTARGET%2F
```&lt;/p&gt;
&lt;p&gt;If the victim is logged in and authorized for `previewElement:123`, Craft creates that exact token.&lt;/p&gt;
&lt;p&gt;## 3) Attacker accesses preview content unauthenticated
```bash
curl -i &amp;#39;https://TARGET/news/known-entry-slug?token=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Expected vulnerable behavior:&lt;/p&gt;
&lt;p&gt;- Response renders preview/unpublis…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Craft CMS has a CSRF issue in the preview token endpoint at `/actions/preview/create-token`.  The endpoint accepts an attacker-supplied `previewToken`.&lt;/p&gt;
&lt;p&gt;Because the action does not require POST and does not enforce a CSRF token, an attacker can force a logged-in victim editor to mint a preview token chosen by the attacker.&lt;/p&gt;
&lt;p&gt;That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Preconditions
- Victim is logged in to Craft control panel.
- Victim has active preview authorization in session for target content (e.g., opened/edited an entry).
- The attacker must know the target’s `canonicalId` and public URL path of that entry.&lt;/p&gt;
&lt;p&gt;## 1) Attacker prepares a fixed token
Use any 32-character value, for example:
```text
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
```&lt;/p&gt;
&lt;p&gt;## 2) CSRF victim into minting that token
Send the victim a link (or top-level redirect) such as:
```text
https://TARGET/actions/preview/create-token?elementType=craft%5Celements%5CEntry&amp;amp;canonicalId=123&amp;amp;siteId=1&amp;amp;previewToken=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&amp;amp;redirect=https%3A%2F%2FTARGET%2F
```&lt;/p&gt;
&lt;p&gt;If the victim is logged in and authorized for `previewElement:123`, Craft creates that exact token.&lt;/p&gt;
&lt;p&gt;## 3) Attacker accesses preview content unauthenticated
```bash
curl -i &amp;#39;https://TARGET/news/known-entry-slug?token=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Expected vulnerable behavior:&lt;/p&gt;
&lt;p&gt;- Response renders preview/unpublis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vg3j-hpm9-8v5v</guid>
    </item>
  </channel>
</rss>
