Quick answers
- Is CVE-2026-47234 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47234 being exploited in the wild.
- How severe is CVE-2026-47234?
- Medium severity, with a CVSS score of 4.4, published 29 May 2026.
- Which products and versions are affected?
- Admidio <= 5.0.9; admidio/admidio (Packagist) <= 5.0.9, ECOSYSTEM:introduced=0,fixed=5.0.10.
- Is there a fix for CVE-2026-47234?
- Yes. admidio/admidio (Packagist): upgrade to 5.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47234 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-47234?
- Check whether you run Admidio or admidio/admidio (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- admidio/admidio (Packagist): upgrade to 5.0.10 or later
composer require admidio/admidio:^5.0.10
Technical details
Admidio versions 5.0.9 and earlier are vulnerable to sensitive information disclosure in the logging component. When debug logging is enabled, the `Session::setCookie()` and `Session::start()` methods in `src/Session/Entity/Session.php` write raw cookie values and session IDs to the application log. This includes the `ADMIDIO_*_SESSION_ID` and the persistent `ADMIDIO_*_AUTO_LOGIN_ID`. An attacker with read access to the log files, backups, or log aggregation services can extract these bearer tokens to perform session hijacking or maintain long-term unauthorized access to user accounts. The issue is addressed in version 5.0.10 by redacting these sensitive values before they are committed to the logs.
Affected products
- Admidio Admidio <= 5.0.9
Identifiers
- CVE-2026-47234
- GHSA-mch8-wf3h-6x88
Timeline
- 2026-05-25: disclosed
- 2026-05-29: advisory: GHSA-mch8-wf3h-6x88 published