Admidio writes session IDs and auto-login cookie values to application logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.4 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-47234: 0.17% estimated exploitation activity in the next 30 days; percentile 6.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Vulnerable Code Links - 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 Vulnerable Code What Does The Code Mean 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. Why The Code Is Vulnerable 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 outputs.…

Published by the source

29 May 2026, 22:07 UTC

Last modified by the source

14 Jun 2026, 17:45 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mch8-wf3h-6x88

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47234

Advisory: Admidio writes session IDs and auto-login cookie values to application logs
IDs: CVE-2026-47234, GHSA-mch8-wf3h-6x88
Record: https://patchnext.com/advisories/cve-2026-47234 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected <= 5.0.9; fixed in 5.0.10

## Suggested inspection (read-only)
- Packagist admidio/admidio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on admidio/admidio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mch8-wf3h-6x88 (GitHub-reviewed advisory GHSA-mch8-wf3h-6x88 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9)

Commands are suggestions: review each one before running it.