Admidio session hijack persists after password reset
Affects Admidio versions before 5.0.18 where a live session or remember-me cookie stays valid after a password reset. Fixed in 5.0.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.18
- Who is exposed
- Specific setups only
Summary
Admidio does not properly end existing sessions after a forgot-password reset, so an attacker who already holds a victim's session or remember-me cookie can stay logged in after the victim resets the password. The attacker reaches this remotely over the network with low-privilege access, and it requires the victim to take the password reset action.
Written by a model
Original description
Admidio before 5.0.18 contains an insufficient session expiration vulnerability that allows attackers to keep account access after a forgot-password reset because User::setPassword() deletes sessions using the visitor ID instead of the reset user's usr_id. Attackers already holding a victim's session or remember-me cookie can continue using it after the victim resets the password, keeping authenticated access to the account.
Who should check
Teams running Admidio 5.0.17 or earlier, especially sites that let members reset forgotten passwords by email.
“Affecting admidio < 5.0.18”
What to do
Check whether your setup matches what the bug needs.
Admidio versions before 5.0.18 are affected. The victim must complete the emailed forgot-password reset. The attacker already holds the victim's session cookie or remember-me cookie.Upgrade to a fixed version: 5.0.18.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134257 (Admidio before 5.0.18 Insufficient Session Expiration After Password Reset), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134257 (entry last updated 2026-11-21):
Affected:
- Admidio admidio: fixed in 5.0.18
Fixed versions: 5.0.18.
Conditions (all must be true for the bug to be hit):
- Admidio versions before 5.0.18 are affected. (source: https://www.vulncheck.com/advisories/admidio-before-5.0.18-insufficient-session-expiration-after-password-reset)
- The victim must complete the emailed forgot-password reset. (source: https://github.com/Admidio/admidio/security/advisories/GHSA-gjx3-9xm2-p599)
- The attacker already holds the victim's session cookie or remember-me cookie. (source: https://github.com/Admidio/admidio/security/advisories/GHSA-gjx3-9xm2-p599)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-134257 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134257 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Admidio/admidio/security/advisories/GHSA-gjx3-9xm2-p599
- https://www.vulncheck.com/advisories/admidio-before-5.0.18-insufficient-session-expiration-after-password-reset
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134257
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134257"}.Affected versions
- Admidio admidiofixed in 5.0.18
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Admidio/admidio · Advisory GHSA-gjx3-9xm2-p599 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134257 |
| Record | NVD · CVE-2026-134257 |
| Other links 1 | |
| Link | vulncheck.com · advisories/admidio-before-5.0.18-insufficient-session-expiration-after-password-reset |
Questions about CVE-2026-134257
Is CVE-2026-134257 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
After a victim resets their password through the emailed forgot-password flow, sessions that were already active are not properly expired. Someone who already holds the victim's session cookie or remember-me cookie can keep authenticated access to the account after the reset.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134257?
admidio: before 5.0.18.
Source: cve.now feed data
Am I affected, and how do I check?
Admidio versions before 5.0.18 are affected. The exposure needs a live session cookie or remember-me cookie that an attacker already holds, and a password reset completed by the victim through the emailed reset flow. To check your version, look at the Admidio version shown in the site's administration or footer information.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134257?
Upgrade Admidio to version 5.0.18 or later, which is the fixed version listed for this vulnerability.
Source: vulncheck.com, github.com
Related
- CVE-2026-134258Admidio 5.0.0 before 5.0.18 Path Traversal to Stored XSS via File Rename
- CVE-2026-134262Admidio 5.0.0 before 5.0.18 Stored XSS via Role Name in Profile View
- CVE-2026-82657Admidio before 5.0.12 Authentication Bypass via RSS feeds
- CVE-2026-109329Admidio 4.3.2 through 4.3.17 and 5.0.0 before 5.0.15 Cross-Organization Access Control Bypass via members_assignment.php
- CVE-2026-134254Admidio 5.0.0 before 5.0.18 Path Traversal via Documents & Files Rename
- CVE-2026-134261Admidio 5.0.17 IDOR in mylist.php Exposes Private List Configurations
No corrections so far. Something wrong on this page? Report an error.