Vulnerability in CI4MS (CVE-2026-39393)
Summary
Vulnerability in CI4MS (CVE-2026-39393). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.31.4.0 or later.
Original description
The description as published by the source.
CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to 0.31.4.0, the install route guard in ci4ms relies solely on a volatile cache check (cache('settings')) combined with .env file existence to block post-installation access to the setup wizard. When the database is temporarily unreachable during a cache miss (TTL expiry or admin-triggered cache clear), the guard fails open, allowing an unauthenticated attacker to overwrite the .env file with attacker-controlled database credentials, achieving full application takeover. This vulnerability is fixed in 0.31.4.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-39393 has been found in CI4MS.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade CI4MS to 0.31.4.0 or later.
If unsure, ask your IT team or search "CI4MS CVE-2026-39393" on the vendor's site.
CVE-2026-39393 (CI4MS) — CWE-306 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.31.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in CI4MS.
Check the vendor advisory for the affected versions of CI4MS.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 0.31.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CI4MS' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'CI4MS' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CI4MSを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CI4MS to 0.31.4.0ステージング環境で 0.31.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov