Cve-2026-39394 - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/cve-2026-39394/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 02 Jan 2024 12:00:00 +0000CI4MS .env File Injection Vulnerability (CVE-2026-39394)https://feed.craftedsignal.io/briefs/2024-01-02-ci4ms-env-injection/Tue, 02 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-02-ci4ms-env-injection/CI4MS versions prior to 0.31.4.0 are vulnerable to .env file injection via the Install::index() controller due to insufficient input validation and bypassed CSRF protection, allowing attackers to inject arbitrary configuration directives.CI4MS is a CodeIgniter 4-based CMS skeleton designed to provide a production-ready, modular architecture with features like RBAC authorization and theme support. Versions prior to 0.31.4.0 contain a critical vulnerability (CVE-2026-39394) within the Install::index() controller. This controller reads the 'host' POST parameter without proper validation and passes it directly to the updateEnvSettings() function. This function, in turn, uses preg_replace() to write the value into the .env file. The lack of newline character stripping in the input allows an attacker to inject arbitrary configuration directives. Furthermore, the installation routes have CSRF protection explicitly disabled, and the InstallFilter can be bypassed when the cache('settings') is empty, such as during initial deployment or after cache expiry. This vulnerability allows unauthenticated attackers to modify the application's configuration, leading to potentially complete system compromise. CI4MS deployments are vulnerable until upgraded to version 0.31.4.0 or later.

Attack Chain

  1. An unauthenticated attacker sends a POST request to the /install route with a malicious 'host' parameter.
  2. The Install::index() controller receives the POST request.
  3. The controller bypasses CSRF protection due to it being explicitly disabled.
  4. The InstallFilter is bypassed because the cache('settings') is empty (e.g., on a fresh deployment).
  5. The 'host' parameter, containing injected configuration directives with newline characters, is passed to the updateEnvSettings() function.
  6. The updateEnvSettings() function uses preg_replace() to write the attacker-controlled 'host' parameter into the .env file without proper sanitization.
  7. The injected configuration directives are written into the .env file, modifying the application's configuration.
  8. The attacker can now leverage the modified configuration for further malicious activities, such as gaining unauthorized access, escalating privileges, or injecting malicious code.

Impact

Successful exploitation of this vulnerability allows an attacker to inject arbitrary configuration directives into the .env file. This can lead to a wide range of consequences, including but not limited to: database credential compromise, modification of application behavior, remote code execution, and complete system takeover. The number of potential victims is dependent on the number of CI4MS deployments running vulnerable versions (pre-0.31.4.0). Targeted sectors are likely to be diverse, reflecting the broad range of applications for which CI4MS is used.

Recommendation

  • Upgrade CI4MS to version 0.31.4.0 or later to patch CVE-2026-39394.
  • Monitor web server logs for POST requests to the /install route containing newline characters in the 'host' parameter to detect potential exploitation attempts. Implement the provided Sigma rules to detect this activity.
  • Implement strict input validation on all user-supplied data, especially for parameters that are used to modify configuration files.
  • Ensure that CSRF protection is enabled and functioning correctly for all sensitive routes, including installation routes.
]]>highadvisoryci4mscodeigniterenv-injectioncve-2026-39394