<?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://db.gcve.eu</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>Tue, 06 Oct 2026 09:17:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-47234</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-47234</link>
      <description>&lt;p&gt;Admidio is an open-source user management solution. Prior to version 5.0.10, when debug logging is enabled, `Session::setCookie()` logs full cookie values and `Session::start()` logs the current session ID. In a real Admidio deployment this includes both the active session cookie and the persistent auto-login cookie. Anyone with access to the log sink can recover live bearer-style credentials from the logs. Version 5.0.10 contains a fix.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Admidio is an open-source user management solution. Prior to version 5.0.10, when debug logging is enabled, `Session::setCookie()` logs full cookie values and `Session::start()` logs the current session ID. In a real Admidio deployment this includes both the active session cookie and the persistent auto-login cookie. Anyone with access to the log sink can recover live bearer-style credentials from the logs. Version 5.0.10 contains a fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-47234</guid>
    </item>
    <item>
      <title>GHSA-mch8-wf3h-6x88 — Admidio writes session IDs and auto-login cookie values to application logs</title>
      <link>https://db.gcve.eu/vuln/ghsa-mch8-wf3h-6x88</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: admidio/admidio&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When debug logging is enabled, `Session::setCookie()` logs full cookie values and `Session::start()` logs the current session ID. In a real Admidio deployment this includes both the active session cookie and the persistent auto-login cookie. Anyone with access to the log sink can recover live bearer-style credentials from the logs.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code Links&lt;/p&gt;
&lt;p&gt;- https://github.com/Admidio/admidio/blob/v5.0.9/src/Session/Entity/Session.php#L533-L540
- https://github.com/Admidio/admidio/blob/v5.0.9/src/Session/Entity/Session.php#L615-L617&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;```php
// src/Session/Entity/Session.php
$gLogger-&amp;gt;info(&amp;#39;Set Cookie!&amp;#39;, array(
&amp;#39;name&amp;#39; =&amp;gt; $name,
&amp;#39;value&amp;#39; =&amp;gt; $value,
&amp;#39;expire&amp;#39; =&amp;gt; $expire,
&amp;#39;path&amp;#39; =&amp;gt; $path,
&amp;#39;domain&amp;#39; =&amp;gt; $domain,
&amp;#39;secure&amp;#39; =&amp;gt; $secure,
&amp;#39;httpOnly&amp;#39; =&amp;gt; $httpOnly,
&amp;#39;sameSite&amp;#39; =&amp;gt; &amp;#39;lax&amp;#39;
));
...
session_start();
$gLogger-&amp;gt;info(&amp;#39;Session Started!&amp;#39;, array(
&amp;#39;name&amp;#39; =&amp;gt; $sessionName,
&amp;#39;limit&amp;#39; =&amp;gt; $limit,
&amp;#39;path&amp;#39; =&amp;gt; $path,
&amp;#39;domain&amp;#39; =&amp;gt; $domain,
&amp;#39;secure&amp;#39; =&amp;gt; $secure,
&amp;#39;httpOnly&amp;#39; =&amp;gt; $httpOnly,
&amp;#39;sameSite&amp;#39; =&amp;gt; &amp;#39;lax&amp;#39;,
&amp;#39;sessionId&amp;#39; =&amp;gt; session_id()
));
```&lt;/p&gt;
&lt;p&gt;## What Does The Code Mean&lt;/p&gt;
&lt;p&gt;Every time Admidio sets a cookie, it writes the raw cookie value to the application log. When a session starts, it writes the active session identifier too.&lt;/p&gt;
&lt;p&gt;## Why The Code Is Vulnerable&lt;/p&gt;
&lt;p&gt;Session IDs and persistent auto-login values are credentials. Logging them turns the log file into a credential store and expands the trust boundary to anyone who can read logs, backups, or external log aggregation o…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: admidio/admidio&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When debug logging is enabled, `Session::setCookie()` logs full cookie values and `Session::start()` logs the current session ID. In a real Admidio deployment this includes both the active session cookie and the persistent auto-login cookie. Anyone with access to the log sink can recover live bearer-style credentials from the logs.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code Links&lt;/p&gt;
&lt;p&gt;- https://github.com/Admidio/admidio/blob/v5.0.9/src/Session/Entity/Session.php#L533-L540
- https://github.com/Admidio/admidio/blob/v5.0.9/src/Session/Entity/Session.php#L615-L617&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;```php
// src/Session/Entity/Session.php
$gLogger-&amp;gt;info(&amp;#39;Set Cookie!&amp;#39;, array(
&amp;#39;name&amp;#39; =&amp;gt; $name,
&amp;#39;value&amp;#39; =&amp;gt; $value,
&amp;#39;expire&amp;#39; =&amp;gt; $expire,
&amp;#39;path&amp;#39; =&amp;gt; $path,
&amp;#39;domain&amp;#39; =&amp;gt; $domain,
&amp;#39;secure&amp;#39; =&amp;gt; $secure,
&amp;#39;httpOnly&amp;#39; =&amp;gt; $httpOnly,
&amp;#39;sameSite&amp;#39; =&amp;gt; &amp;#39;lax&amp;#39;
));
...
session_start();
$gLogger-&amp;gt;info(&amp;#39;Session Started!&amp;#39;, array(
&amp;#39;name&amp;#39; =&amp;gt; $sessionName,
&amp;#39;limit&amp;#39; =&amp;gt; $limit,
&amp;#39;path&amp;#39; =&amp;gt; $path,
&amp;#39;domain&amp;#39; =&amp;gt; $domain,
&amp;#39;secure&amp;#39; =&amp;gt; $secure,
&amp;#39;httpOnly&amp;#39; =&amp;gt; $httpOnly,
&amp;#39;sameSite&amp;#39; =&amp;gt; &amp;#39;lax&amp;#39;,
&amp;#39;sessionId&amp;#39; =&amp;gt; session_id()
));
```&lt;/p&gt;
&lt;p&gt;## What Does The Code Mean&lt;/p&gt;
&lt;p&gt;Every time Admidio sets a cookie, it writes the raw cookie value to the application log. When a session starts, it writes the active session identifier too.&lt;/p&gt;
&lt;p&gt;## Why The Code Is Vulnerable&lt;/p&gt;
&lt;p&gt;Session IDs and persistent auto-login values are credentials. Logging them turns the log file into a credential store and expands the trust boundary to anyone who can read logs, backups, or external log aggregation o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mch8-wf3h-6x88</guid>
    </item>
  </channel>
</rss>
