<?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-15T03:50:09.327274+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-5645</id>
    <title>EUVD-2026-5645</title>
    <updated>2026-10-15T03:50:09.386724+00:00</updated>
    <content>EUVD-2026-5645</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-5645"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-36119</id>
    <title>fkie_cve-2024-36119</title>
    <updated>2026-10-15T03:50:09.386771+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Statamic is a, Laravel + Git powered CMS designed for building websites. In affected versions users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file. This only affects sites matching **all** of the following conditions: 1. Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week), 2. Using the `user:register_form` tag. 3. Using file-based user accounts. (Does not affect users stored in a database.), 4. Has users that have registered during that time period. (Existing users are not affected.). Additionally passwords are only visible to users that have access to read user yaml files, typically developers of the application itself. This issue has been patched in version 5.6.2, however any users registered during that time period and using the affected version range will still have the the `password_confirmation` value in their yaml files. We recommend that affected users have their password reset. System administrators are advised to upgrade their deployments. There are no known workarounds for this vulnerability. Anyone who commits their files to a public git repo, may consider clearing the sensitive data from the git history as it is likely that passwords were uploaded.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-36119"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qvpj-w7xj-r6w9</id>
    <title>GHSA-qvpj-w7xj-r6w9 — Password confirmation stored in plain text via registration form in statamic/cms</title>
    <updated>2026-10-15T03:50:09.386839+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: statamic/cms</p>
<p>Users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file.</p>
<p>### Impact
This only affects sites matching **all** of the following conditions:
- Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week)
- Using the `user:register_form` tag.
- Using file-based user accounts. (Does not affect users stored in a database.)
- Has users that have registered during that time period. (Existing users are not affected.)</p>
<p>The password is only visible to users that have access to read user yaml files, typically developers of the application itself.</p>
<p>### Patches
The issue has been patched in 5.6.2, however any users registered during that time period and using the affected version range will still have the the `password_confirmation` value in their yaml files.</p>
<p>We recommend that affected users have their password reset. The following query can be entered into `php artisan tinker` and will output a list of affected emails:</p>
<p>```php
Statamic\Facades\User::query()-&gt;whereNotNull('password_confirmation')-&gt;get()-&gt;map-&gt;email
```</p>
<p>The following can be entered into `tinker` and will clear both password_confirmation as well as their existing password. They will be required to reset their password before their next login attempt.</p>
<p>```php
Statamic\Facades\User::query()
  -&gt;whereNotNull('password_confirmation')-&gt;get()
  -&gt;each(fn ($user) =&gt; $user-&gt;remove('password_confirmation')-&gt;passwo…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qvpj-w7xj-r6w9"/>
  </entry>
</feed>
