<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T10:58:23.409284+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-362998</id>
    <title>EUVD-2026-362998</title>
    <updated>2026-10-08T10:58:23.464293+00:00</updated>
    <content>EUVD-2026-362998</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-362998"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-29113</id>
    <title>fkie_cve-2026-29113</title>
    <updated>2026-10-08T10:58:23.464333+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-29113"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vg3j-hpm9-8v5v</id>
    <title>GHSA-vg3j-hpm9-8v5v — Craft CMS has a potential information disclosure vulnerability in preview tokens</title>
    <updated>2026-10-08T10:58:23.464372+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: craftcms/cms</p>
<p># Summary</p>
<p>Craft CMS has a CSRF issue in the preview token endpoint at `/actions/preview/create-token`.  The endpoint accepts an attacker-supplied `previewToken`.</p>
<p>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.</p>
<p>That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope.</p>
<p>---</p>
<p>## 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.</p>
<p>## 1) Attacker prepares a fixed token
Use any 32-character value, for example:
```text
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
```</p>
<p>## 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;canonicalId=123&amp;siteId=1&amp;previewToken=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa&amp;redirect=https%3A%2F%2FTARGET%2F
```</p>
<p>If the victim is logged in and authorized for `previewElement:123`, Craft creates that exact token.</p>
<p>## 3) Attacker accesses preview content unauthenticated
```bash
curl -i 'https://TARGET/news/known-entry-slug?token=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
```</p>
<p>Expected vulnerable behavior:</p>
<p>- Response renders preview/unpublis…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vg3j-hpm9-8v5v"/>
  </entry>
</feed>
