# CVE-2026-45139: CI4MS Fileeditor allows deletion and rename of critical application files due to missing extension allowlist on destructive operations

> Authenticated users can delete or rename critical application files, causing persistent denial of service and requiring manual recovery.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-245j-xjvr-xvm5

## What is CVE-2026-45139?

CVE-2026-45139 is a medium-severity path traversal vulnerability in ci4-cms-erp ci4ms, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-45139?

2 open source packages ship an affected version, including ci4-cms-erp/ci4ms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ci4-cms-erp/ci4ms` | Packagist | All versions | 0.31.9.0 |
| `ci4-cms-erp/ci4ms` | Packagist | All versions | 0.31.9.0 |

## How do I fix CVE-2026-45139?

Upgrade ci4-cms-erp/ci4ms to 0.31.9.0 or later.

## Is CVE-2026-45139 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45139 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45139 and fix it if it is affected.

What it is: CVE-2026-45139 is a medium-severity path traversal vulnerability in ci4-cms-erp ci4ms, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45139 exists.

Affected packages and fixed versions:
- ci4-cms-erp/ci4ms (Packagist): affected all versions; fixed in 0.31.9.0
- ci4-cms-erp/ci4ms (Packagist): affected all versions; fixed in 0.31.9.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45139/ (Markdown: https://insights.sbomify.com/CVE-2026-45139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45139
- OSV: https://osv.dev/vulnerability/CVE-2026-45139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45139/
Summaries are generated and may contain mistakes; the official description above is the record.