Most recent entries from all

EUVD-2026-278728

2026-10-06T00:30:00.912122+00:00

EUVD-2026-278728

fkie_cve-2026-34572

2026-10-06T00:30:00.912162+00:00

CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to version 0.31.0.0, the application fails to immediately revoke active user sessions when an account is deactivated. Due to a logic flaw in the backend design, account state changes are enforced only during authentication (login), not for already-established sessions. The system implicitly assumes that authenticated users remain trusted for the lifetime of their session. There is no session expiration or account expiration mechanism in place, causing deactivated accounts to retain indefinite access until the user manually logs out. This behavior breaks the intended access control policy and results in persistent unauthorized access, representing a critical security flaw. This issue has been patched in version 0.31.0.0.

GHSA-8fq3-c5w3-pj3q — CI4MS: Account Deactivation Module Grants Full Persistent Unauthorized Access for All‑Roles via Improper Session Invali…

2026-10-06T00:30:00.912199+00:00

Affected: Packagist: ci4-cms-erp/ci4ms

## Summary ### Vulnerability: Improper Session Invalidation on Account Deactivation (Broken Access Control / Logic Flaw) - This vulnerability is caused by a backend logic flaw that maintains a false trust assumption that already-authenticated users remain trustworthy, even after their accounts are explicitly deactivated. As a result, administrative security actions do not behave as intended, allowing persistent unauthorized access.

### Description The application fails to immediately revoke active user sessions when an account is deactivated. Due to a logic flaw in the backend design, account state changes are enforced only during authentication (login), not for already-established sessions.

The system implicitly assumes that authenticated users remain trusted for the lifetime of their session. There is no session expiration or account expiration mechanism in place, causing deactivated accounts to retain indefinite access until the user manually logs out. This behavior breaks the intended access control policy and results in persistent unauthorized access, representing a critical security flaw.

### Affected Functionality - User session management and authentication logic - Account deactivation mechanism - All authenticated endpoints, including administrative and content interfaces

### Attack Scenario - A user logs into the application. - An administrator deactivates the user account. - The user remains fully logged in and can continue performing all actions allowed by th…