<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T01:55:11.460153+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/fkie_cve-2026-47228</id>
    <title>fkie_cve-2026-47228</title>
    <updated>2026-09-30T01:55:11.516231+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Admidio is an open-source user management solution. `modules/registration.php` mode `send_login` regenerates a random password for `user_uuid_assigned`, stores its bcrypt hash in `adm_users.usr_password`, and emails the cleartext to that user. Every other state-changing mode in the same file (`assign_member`, `assign_user`, `delete_user`, `create_user`) calls `SecurityUtils::validateCsrfToken($_POST['adm_csrf_token'])` first; the `send_login` branch does not. Prior to version 5.0.10, page visited by a registration-administrator can issue the request as a top-level navigation, the browser sends the admin's `SameSite=Lax` cookies, and the server resets the chosen user's password without any further interaction from the admin. Version 5.0.10 fixes the issue.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-47228"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-mx25-j3rc-6w2w</id>
    <title>GHSA-mx25-j3rc-6w2w — Admidio's CSRF in registration `send_login` mode resets arbitrary user passwords</title>
    <updated>2026-09-30T01:55:11.516347+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: admidio/admidio</p>
<p>## Summary</p>
<p>`modules/registration.php` mode `send_login` regenerates a random password for `user_uuid_assigned`, stores its bcrypt hash in `adm_users.usr_password`, and emails the cleartext to that user. Every other state-changing mode in the same file (`assign_member`, `assign_user`, `delete_user`, `create_user`) calls `SecurityUtils::validateCsrfToken($_POST['adm_csrf_token'])` first; the `send_login` branch does not. A page visited by a registration-administrator can issue the request as a top-level navigation, the browser sends the admin's `SameSite=Lax` cookies, and the server resets the chosen user's password without any further interaction from the admin.</p>
<p>## Details</p>
<p>### Vulnerable Code</p>
<p>`modules/registration.php:124-138`:</p>
<p>```php
} elseif ($getMode === 'send_login') {
    // User already exists and has a login than sent access data with a new password
    $user = new User($gDb, $gProfileFields);
    $user-&gt;readDataByUuid($getUserUUIDAssigned);
    $user-&gt;sendNewPassword();</p>
<p>// delete the registration because it isn't necessary anymore
    $registrationUser-&gt;notSendEmail();
    $registrationUser-&gt;delete();
    admRedirect(ADMIDIO_URL.FOLDER_MODULES.'/registration.php');
    // =&gt; EXIT
}
```</p>
<p>The four sibling branches all begin with `SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);` — for example `delete_user` at lines 110-118:</p>
<p>```php
} elseif ($getMode === 'delete_user') {
    // check the CSRF token of the form against the session token
    SecurityU…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-mx25-j3rc-6w2w"/>
  </entry>
</feed>
