CVE-2026-129706

vulnerability-lookup: Session Persists After Password Change (CWE-613)

Published Nov 16, 2026 CVSS 4.0 · 5.3 Medium EPSS n/a KEV · Not listed
Description
In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation.

The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application.

The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely.

Analysis

AI-generated

Technical impact

The Flask-Login session identifier was originally the plain numeric user ID, so the cookie contained no credential‑derived value. After a user changed their password, the session remained valid and the user_loader accepted the old ID without verifying that the session matched the new credentials. As a result, an attacker who had already obtained a valid session cookie could continue to act as the victim without interruption, even after the victim performed a password change or an administrator reset the password. The fix binds the session ID to the current password hash, forcing a mismatch and rejecting the session when the password changes, which effectively logs out all other sessions but keeps the user's own session fresh. The attack requires that the attacker has already captured a session cookie for the target user. Although obtaining that cookie might involve XSS, session hijacking, or exposure of a feed or API key, it does not require any further authentication or configuration changes beyond a standard deployment. The vulnerability therefore prevents a user’s password change from revoking access. The risk level, as reflected by the CVSS score of 5.3, is moderate. Because the EPSS score is unavailable and the vulnerability is not listed in the CISA KEV catalog, the likelihood of widespread exploitation is uncertain. Nevertheless, the persistence of an authenticated session can allow prolonged compromise, especially if the attacker already has a compromised cookie from another vector. Agents should treat the vulnerability as a moderate‑severity risk that should be remediated promptly.

Affected Systems

The vulnerability is present in the vulnerability‑lookup product, specifically within the Flask session management components: User.get_id() in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. No specific product version range is provided, so any deployment using the unpatched session logic is affected.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and the lack of an EPSS score means exploit probability cannot be quantified here. The vulnerability is not in the CISA KEV list, suggesting no widely observed exploitation yet. Attackers can only exploit it if they have a valid session cookie for the victim, which they can acquire via cross‑site scripting, session hijacking, or exposure of a feed or API key. Once in possession of the cookie, the attacker can maintain access indefinitely until the victim changes the password and a new digest is generated, unless the session handling logic is updated. Hence, the attacker’s advantage is the persistence of the session, not the ability to elevate privileges or bypass authentication outright.

Remediation

Vendor Solution

The session identifier is now bound to the user's current password hash. User.get_id() returns a composite string of the form '<user_id>:<digest>', where the digest is an HMAC-SHA256 of the stored password hash keyed with the application SECRET_KEY. The load_user callback validates that the digest in the session matches the digest computed from the user's current password hash using a constant-time comparison (hmac.compare_digest). If the password has changed, the digest no longer matches and the session is rejected, effectively logging out all sessions that were opened under the previous credential. When a user changes their own password through the profile page, they are immediately re-authenticated via login_user() so their current session is renewed with the new digest while all other sessions are invalidated.


OpenCVE Recommended Actions

  • Upgrade vulnerability‑lookup to include the session identifier change that binds the session to the current password hash, as described in the provided reference commit.
  • If upgrading immediately is not possible, modify the password change flow to call login_user() after updating the password so that the user’s own session is renewed with the new digest while all other sessions are invalidated.
  • For older installations that lack the digest binding, implement middleware that checks the session ID against a hash of the current password or force a global session revocation whenever a password reset or change occurs.

Generated by OpenCVE AI on November 16, 2026 at 10:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation. The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application. The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely.
Title vulnerability-lookup: Session Persists After Password Change (CWE-613)
First Time appeared Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup
Weaknesses CWE-613
CPEs cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*
Vendors & Products Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
CIRCL
Published
Updated
Nov 16, 2026, 8:46 AM
Reserved
Nov 16, 2026, 8:46 AM
Status
Received
Published
Nov 16, 2026, 9:17 AM
Modified
Nov 16, 2026, 9:17 AM