The session management layer of the application uses a static numeric user ID as the session identifier via the `User.get id()` method in `website/models/user.py` and the `load user` callback in `website/web/views/session mgmt.py`. Since the session ID is not bound to user credentials, it remains valid indefinitely, even after password changes, account recoveries, or administrator-initiated resets. An attacker with a previously obtained valid session can maintain full authenticated access to a user's profile and role-gated functionality. This issue also affected sessions opened via feed or API keys prior to commit 3605d5b6.