Vulnerability in ci4-cms-erp/ci4ms (CVE-2026-45139)
Summary
Vulnerability in ci4-cms-erp/ci4ms (CVE-2026-45139). Data can be tampered with by attackers. Exploitable via saveFile. Mitigation: upgrade to 0.31.9.0 or later.
Original description
The description as published by the source.
CI4MS is a CodeIgniter 4-based content management system skeleton. Prior to version 0.31.9.0, the Fileeditor module enforces an extension allowlist (['css','js','html','txt','json','sql','md']) on content-write operations (saveFile, createFile), but two destructive endpoints — deleteFileOrFolder and renameFile — never validate the extension of the source path. A backend user with file-editor permissions can therefore unlink or rename any file inside the project root that is not explicitly listed in the small $hiddenItems blocklist. Critical framework files such as app/Config/Routes.php, app/Config/App.php, app/Config/Database.php, app/Config/Filters.php, public/index.php, and public/.htaccess all live outside that blocklist and can be destroyed, producing a persistent denial of service that requires filesystem-level redeployment to recover. Version 0.31.9.0 patches the issue.
Source: GitHub Security Advisories (Global) 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-45139 has been found in ci4-cms-erp/ci4ms.
Attackers can target a specific entry point like saveFile over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade ci4-cms-erp/ci4ms to 0.31.9.0 or later.
If unsure, ask your IT team or search "ci4-cms-erp/ci4ms CVE-2026-45139" on the vendor's site.
CVE-2026-45139 (ci4-cms-erp/ci4ms) — CWE-73 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: saveFile / createFile / deleteFileOrFolder / renameFile
Patched: 0.31.9.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-73) exists in ci4-cms-erp/ci4ms. Attackers reach the vulnerable code path via saveFile.
Check the vendor advisory for the affected versions of ci4-cms-erp/ci4ms. Attack surface: saveFile / createFile / deleteFileOrFolder / renameFile.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 0.31.9.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 'ci4-cms-erp/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 'ci4-cms-erp/ci4ms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ci4-cms-erp/ci4msを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ci4-cms-erp/ci4ms to 0.31.9.0ステージング環境で 0.31.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com