{"answers":{"affected":"2 open source packages ship an affected version, including ci4-cms-erp/ci4ms.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45139 exists.","fix":"Upgrade ci4-cms-erp/ci4ms to 0.31.9.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-45139 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45139 exists.\n\nAffected packages and fixed versions:\n- ci4-cms-erp/ci4ms (Packagist): affected all versions; fixed in 0.31.9.0\n- ci4-cms-erp/ci4ms (Packagist): affected all versions; fixed in 0.31.9.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45139/ (Markdown: https://insights.sbomify.com/CVE-2026-45139/index.md)","id":"CVE-2026-45139","markdown":"https://insights.sbomify.com/CVE-2026-45139/index.md","name":"CVE-2026-45139","record":{"aliases":["GHSA-245j-xjvr-xvm5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"CI4MS CMS","requires_auth":"high_privilege","summary":"Authenticated users can delete or rename critical application files, causing persistent denial of service and requiring manual recovery.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CI4MS Fileeditor allows deletion and rename of critical application files due to missing extension allowlist on destructive operations","id":"CVE-2026-45139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Chamilo LMS CStudio upload flow allows unauthenticated remote code execution","id":"CVE-2026-45140"},"packages":[{"ecosystem":"Packagist","fixed":["0.31.9.0"],"introduced":["0"],"last_affected":[],"package":"ci4-cms-erp/ci4ms","purl":null,"source":"GHSA-245j-xjvr-xvm5"},{"ecosystem":"Packagist","fixed":["0.31.9.0"],"introduced":["0"],"last_affected":[],"package":"ci4-cms-erp/ci4ms","purl":"pkg:composer/ci4-cms-erp/ci4ms","source":"GHSA-245j-xjvr-xvm5"}],"prev":{"headline":"CI4MS: Stored XSS in Blog Content via Broken `html_purify` Validation Rule","id":"CVE-2026-45138"},"products":["ci4ms"],"published":"2026-07-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["ci4-cms-erp"]},"summary":"Authenticated users can delete or rename critical application files, causing persistent denial of service and requiring manual recovery.","url":"https://insights.sbomify.com/CVE-2026-45139/"}