ci4-cms-erp/ci4ms
Affected
- introduced
0.26.0, fixed0.31.8.0(ecosystem)
Fixed versions
0.31.8.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: 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. When an admin deactivates a user (active=0) after they have already logged in:
auth()->loggedIn() still returns true!$user->activeEvidence
<img width="981" height="654" alt="image" src="https://github.com/user-attachments/assets/6f75d144-5bcf-4a3f-bc35-bb0715c3ed05" />
Impact
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?.
Medium Basis: The source's own band: MODERATE
0.26.0, fixed 0.31.8.0 (ecosystem)0.31.8.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0