Quick answers
- Is CVE-2026-39389 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39389 being exploited in the wild.
- How severe is CVE-2026-39389?
- Medium severity, with a CVSS score of 6.7, published 8 April 2026.
- Which products and versions are affected?
- ci4-cms-erp/ci4ms (Packagist) ECOSYSTEM:introduced=0,fixed=0.31.4.0.
- Is there a fix for CVE-2026-39389?
- Yes. ci4-cms-erp/ci4ms (Packagist): upgrade to 0.31.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39389 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39389?
- Check whether you run ci4-cms-erp/ci4ms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ci4-cms-erp/ci4ms (Packagist): upgrade to 0.31.4.0 or later
composer require ci4-cms-erp/ci4ms:^0.31.4.0
Technical details
An improper authorization vulnerability exists in the Fileeditor controller of CI4MS. While the application defines a 'hiddenItems' array to protect sensitive files like .env and composer.json, this check was only implemented in the directory listing method (listFiles). Other API endpoints—including readFile, saveFile, deleteFileOrFolder, renameFile, and createFile—lacked these checks. A network-based attacker with backend 'fileeditor.read' privileges can exfiltrate secrets from the .env file, while those with 'fileeditor.update' privileges can overwrite composer.json to achieve remote code execution (RCE) via composer scripts. Additionally, CSRF protection was explicitly disabled for these routes, increasing the risk of exploitation. The issue is fixed in version 0.31.4.0.
Affected products
- ci4-cms-erp CI4MS < 0.31.4.0
Identifiers
- CVE-2026-39389
- GHSA-9rxp-f27p-wv3h
Timeline
- 2026-04-07: advisory: GitHub Security Advisory published
- 2026-04-08: disclosed: CVE-2026-39389 published to NVD
- 2026-04-08: patched: Vulnerability fixed in version 0.31.4.0