<?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-14T13:18:54.329188+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-277236</id>
    <title>EUVD-2026-277236</title>
    <updated>2026-10-14T13:18:54.380943+00:00</updated>
    <content>EUVD-2026-277236</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-277236"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33159</id>
    <title>fkie_cve-2026-33159</title>
    <updated>2026-10-14T13:18:54.380977+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Craft CMS is a content management system (CMS). From version 4.0.0-RC1 to before version 4.17.8 and from version 5.0.0-RC1 to before version 5.9.14, guest users can access Config Sync updater index, obtain signed data, and execute state-changing Config Sync actions (regenerate-yaml, apply-yaml-changes) without authentication. This issue has been patched in versions 4.17.8 and 5.9.14.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-33159"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6mrr-q3pj-h53w</id>
    <title>GHSA-6mrr-q3pj-h53w — Craft CMS: Unauthenticated Users Can Perform Restricted Project Config Sync Operations</title>
    <updated>2026-10-14T13:18:54.381009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: craftcms/cms</p>
<p>### Summary
Guest users can access Config Sync updater `index`, obtain signed `data`, and execute state-changing Config Sync actions (`regenerate-yaml`, `apply-yaml-changes`) without authentication.</p>
<p>### Details</p>
<p>`ConfigSyncController` extends `BaseUpdaterController`, and the base updater is anonymously accessible for control panel requests.  `index` emits signed updater state (`data`), which can be reused by guests in subsequent requests.</p>
<p>Sensitive actions that are reachable via this method are `actionApplyYamlChanges`, `actionRegenerateYaml`, `applyExternalChanges`, and  `regenerateExternalConfig`.</p>
<p>#### Reproduction steps</p>
<p>1. Guest POST to:</p>
<p>http POST /admin/actions/config-sync/index</p>
<p>2. Extract data from returned JS state:</p>
<p>Craft.updater = ... setState({"data":"&lt;signedData&gt;", ...});</p>
<p>3. Reuse data as a guest:</p>
<p>```
  POST /admin/actions/config-sync/regenerate-yaml
  data=&lt;signedData&gt;&amp;&lt;csrfParam&gt;=&lt;csrfToken&gt;
```</p>
<p>or</p>
<p>```
  POST /admin/actions/config-sync/apply-yaml-changes
  data=&lt;signedData&gt;&amp;&lt;csrfParam&gt;=&lt;csrfToken&gt;
```</p>
<p>4. Observe completed response and state/file changes.</p>
<p>### Impact</p>
<p>Unauthenticated users can execute project configuration sync operations that should be restricted to trusted admin/deployment contexts.</p>
<p>Depending on the pending YAML/config state, this can cause unauthorized config state transitions and a service integrity risk.</p>
<p>### Resources</p>
<p>https://github.com/craftcms/cms/commit/7f0ead833f7</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6mrr-q3pj-h53w"/>
  </entry>
</feed>
