CVE-2026-41203
Zip Slip Vulnerability in CI4MS CMS
Publication date: 2026-05-07
Last updated on: 2026-05-07
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ci4-cms-erp | ci4ms | to 0.31.5.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an authenticated backend user with theme create permission to achieve remote code execution by uploading malicious ZIP archives that write files to arbitrary filesystem locations, including the public web root.
Such a compromise can lead to full server control, including access to sensitive data such as database credentials stored in configuration files.
This level of unauthorized access and potential data exposure can result in violations of data protection regulations like GDPR and HIPAA, which require strict controls over personal and sensitive data.
Organizations using vulnerable versions prior to 0.31.5.0 risk non-compliance due to possible data breaches, unauthorized data access, and loss of data integrity and availability.
Can you explain this vulnerability to me?
The vulnerability exists in the ci4ms Theme::upload function in versions prior to 0.31.5.0. It is a Zip Slip path traversal flaw that allows an authenticated backend user with theme creation permissions to upload specially crafted ZIP archives. These ZIP files contain entries with directory traversal sequences that bypass validation and extract files outside the intended directory.
This flaw enables the attacker to write files to arbitrary locations on the filesystem, including the public web root, allowing them to drop malicious PHP files and achieve remote code execution (RCE). The root cause is the lack of validation on ZIP entry names before extraction.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to full server compromise. An attacker can upload a PHP shell to the public web root, enabling remote code execution.
- Complete control over the server hosting the application.
- Access to sensitive data such as database credentials stored in configuration files like .env.
- Ability to modify or delete site content, potentially defacing the website or injecting malicious content.
- Severe impacts on confidentiality, integrity, and availability of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of unauthorized PHP files uploaded via the Theme upload functionality, especially those placed outside the intended directories such as under the public web root.
Since the vulnerability involves ZIP archive extraction without validating entry names, you can look for suspicious ZIP files uploaded by authenticated users with theme creation permissions.
To detect exploitation attempts or presence of malicious files, you can run commands to find recently created or modified PHP files in web-accessible directories. For example:
- find /path/to/ci4ms/public -name '*.php' -mtime -7 -ls
- grep -r 'shell' /path/to/ci4ms/public
Additionally, monitoring web server logs for unusual requests to newly uploaded PHP files or unexpected URLs can help detect exploitation.
What immediate steps should I take to mitigate this vulnerability?
The immediate and most effective mitigation step is to upgrade the ci4ms installation to version 0.31.5.0 or later, where this vulnerability has been patched.
Until the upgrade can be performed, restrict or disable the theme creation permission for authenticated backend users to prevent exploitation.
Review and remove any suspicious PHP files that may have been uploaded via the vulnerable Theme::upload function.
Implement monitoring of file uploads and web server logs to detect any attempts to exploit this vulnerability.