CVE-2026-45139: CWE-73: External Control of File Name or Path in ci4-cms-erp ci4ms
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.
AI Analysis
Technical Summary
The vulnerability in ci4-cms-erp's ci4ms product (CVE-2026-45139) arises from improper validation of file extensions in the Fileeditor module's destructive endpoints `deleteFileOrFolder` and `renameFile`. While content-write operations enforce an extension allowlist, these two endpoints do not validate the source file's extension. As a result, a backend user with file-editor permissions can rename or delete any file within the project root that is not explicitly blocked by a small hidden items list. Critical framework files such as configuration and public entry point files are vulnerable, enabling persistent denial of service that requires filesystem-level redeployment to recover. The vulnerability affects all versions prior to 0.31.9.0, which includes the patch.
Potential Impact
An attacker with backend file-editor permissions can rename or delete critical files outside the allowed extension list, including essential configuration and public files. This can cause a persistent denial of service condition requiring filesystem-level redeployment to restore functionality. There is no impact on confidentiality, but integrity and availability are severely affected.
Mitigation Recommendations
Version 0.31.9.0 of ci4ms patches this vulnerability by properly validating file extensions on the source path for destructive operations. Users should upgrade to version 0.31.9.0 or later to remediate this issue. No other official remediation or temporary fixes are documented. Patch status is not explicitly stated as 'official-fix' in the advisory, but the version bump indicates a fix is available.
CVE-2026-45139: CWE-73: External Control of File Name or Path in ci4-cms-erp ci4ms
Description
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.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/ci4-cms-erp/ci4msRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in ci4-cms-erp's ci4ms product (CVE-2026-45139) arises from improper validation of file extensions in the Fileeditor module's destructive endpoints `deleteFileOrFolder` and `renameFile`. While content-write operations enforce an extension allowlist, these two endpoints do not validate the source file's extension. As a result, a backend user with file-editor permissions can rename or delete any file within the project root that is not explicitly blocked by a small hidden items list. Critical framework files such as configuration and public entry point files are vulnerable, enabling persistent denial of service that requires filesystem-level redeployment to recover. The vulnerability affects all versions prior to 0.31.9.0, which includes the patch.
Potential Impact
An attacker with backend file-editor permissions can rename or delete critical files outside the allowed extension list, including essential configuration and public files. This can cause a persistent denial of service condition requiring filesystem-level redeployment to restore functionality. There is no impact on confidentiality, but integrity and availability are severely affected.
Mitigation Recommendations
Version 0.31.9.0 of ci4ms patches this vulnerability by properly validating file extensions on the source path for destructive operations. Users should upgrade to version 0.31.9.0 or later to remediate this issue. No other official remediation or temporary fixes are documented. Patch status is not explicitly stated as 'official-fix' in the advisory, but the version bump indicates a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T20:44:38.963Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5e33df2a4a8d598937d1fe
Added to database: 07/20/2026, 14:42:39 UTC
Last enriched: 07/20/2026, 14:58:42 UTC
Last updated: 07/21/2026, 04:29:24 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.