Summary
Bludit versions prior to 3.22.0 contain a broken access control issue where active sessions are not invalidated when the associated user account is deleted from the database.
This "ghost session" condition allows revoked or removed users to retain full, unauthorized access to the CMS until their existing session tokens naturally expire or are otherwise invalidated.
Affected context
The vulnerability occurs in Bludit deployments that rely on session-based authentication and perform user account deletion through the application or directly in the database.
In these versions, deleting a user record does not trigger revocation or invalidation of that user's active sessions, so any existing session tokens remain usable.
The risk is most pronounced in environments where user removal is used as a primary revocation mechanism for administrators, editors, or other privileged roles.
Exploit preconditions
- Attack surface: Web-based management interface and any authenticated endpoints of the Bludit CMS.
- Required access: Possession of a valid, authenticated session established before the associated user account is deleted.
- Trigger point: Continued use of the existing session cookie or token after the account has been removed from the database.
- Why exploitation is possible: Session lifecycle management is decoupled from user account state; session validity is not rechecked against the current user store, allowing deleted accounts to remain functionally active via their existing sessions (CWE-285, CWE-613).
Why this happens
The core issue is improper enforcement of access control on long-lived sessions: the system trusts previously issued session tokens without revalidating that the underlying user account still exists or remains authorized.
This maps to CWE-285 (Improper Authorization) because authorization decisions are made solely on the presence of a session token, not on current account state.
It is also related to CWE-613 (Insufficient Session Expiration) in that sessions are not proactively invalidated when a user is removed, leaving a window where revoked users can continue to interact with the system.
At an abstract level, the design fails to couple session management with authorization state changes such as account deletion or revocation.
Potential impact
- Revoked users can continue to access the CMS with their prior level of privilege.
- Unauthorized modification, publication, or deletion of website content may occur.
- Continued access to sensitive configuration data, logs, or administrative functions.
- Evasion of deprovisioning and offboarding controls, impacting compliance and auditability.
- Potential pivot to other systems integrated with or managed by the CMS.
General mitigation guidance
Effective mitigation typically involves tightening the relationship between session state and user authorization state.
Common defensive patterns include:
- Validating on each request (or on a frequent basis) that the user account referenced by a session still exists and remains active.
- Designing session stores so they can be invalidated in bulk for a given user when revocation, account deletion, or role change events occur.
- Implementing explicit revocation flows that terminate all active sessions during deprovisioning or password/role changes.
- Applying reasonably short session lifetimes combined with inactivity timeouts to limit the window of exposure if revocation fails.
- Restricting high-privilege actions to sessions that have been recently reauthenticated or revalidated against current user state.
How teams detect issues like this
Detection can focus on both code-level patterns and runtime behavior:
- Static analysis / code review: Look for authentication logic that validates session tokens but does not check whether the associated user record still exists or is flagged as active.
- Design review: Examine session management flows to confirm that account deletion, role changes, or disablement events propagate to the session store.
- Logging and analytics: Monitor for requests where the user ID in session data does not correspond to any existing account, or appears in a "deleted/disabled" state.
- Policy enforcement: Use automated security testing or CI checks to ensure that account deletion and revocation test cases include validation of active-session invalidation.

