CVE-2026-41891: CI4MS has a Deactivated User Session Bypass (active=0)
Summary The auth filter has the deactivated/banned user check commented out. Details CodeIgniter Shield's loggedIn() re-checks the status field (catching status='banned'), but does not re-check the active field for existing sessions.
Published May 4, 2026 · Updated May 8, 2026
Affected packages
ci4-cms-erp/ci4ms
- Ecosystem
- Composer (PHP)
- Affected
- >= 0.26.0, <= 0.31.7.0
- Fixed in
- 0.31.8.0
- Check
composer show ci4-cms-erp/ci4ms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The auth filter has the deactivated/banned user check commented out.
Details
CodeIgniter Shield's loggedIn() re-checks the status field (catching status='banned'), but does not re-check the active field for existing sessions. When an admin deactivates a user (active=0) after they have already logged in:
- Their session cookie remains valid
auth()->loggedIn()still returnstrue- The commented-out code is the only mechanism that would have checked
!$user->active
Evidence
Impact
- User deactivation does NOT immediately revoke backend access
- Deactivated user retains full access until session expires (default: 7200s)
Additional note
The commented-out block appears to be a deferred placeholder — it was written but disabled from the very first commit that introduced the filter, and has never been active. The later addition of SessionTracker (v0.31.4.0) suggests the dev was aware of the session revocation gap, but account-level deactivation (users.active = 0) remains unenforced. Could you verify if this is intentionally pending or simply forgotten and not documented?.
Credited to dapickle.
References
- https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-5hfv-c864-qcq9
- https://github.com/ci4-cms-erp/ci4ms/commit/2f38284281ce6b435ea42003951f14109ac2cea7
- https://github.com/ci4-cms-erp/ci4ms/releases/tag/0.31.8.0
- https://nvd.nist.gov/vuln/detail/CVE-2026-41891
- https://github.com/advisories/GHSA-5hfv-c864-qcq9
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-45138
CI4MS: Stored XSS in Blog Content via Broken `html_purify` Validation Rule
medium5.4May 18, 2026CVE-2026-45139
CI4MS Fileeditor allows deletion and rename of critical application files due to missing extension allowlist on destructive operations
medium6.5May 18, 2026CVE-2026-45270
CI4MS: Stored XSS in Pages Module Content via Broken html_purify Validation Rule
high8.7May 18, 2026CVE-2026-41890
CI4MS Vulnerable to Arbitrary Database Table Drop via Theme deleteProcess
medium6.9May 4, 2026CVE-2026-41587
CI4MS has Unrestricted PHP File Upload via Theme Installation that Leads to Authenticated Remote Code Execution
high8.6Apr 29, 2026CVE-2026-41201
CI4MS: Backup Management Full Account Takeover for All Roles & Privilege Escalation via Stored DOM Blind XSS
medium6.8Apr 22, 2026
