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.