GHSA-9895-26wr-4fgv: EZsystems Remote code execution in file uploads
This Security Advisory is about a vulnerability in the way eZ Platform and eZ Publish Legacy handles file uploads, which can in the worst case lead to remote code execution (RCE), a very serious threat. An attacker would need access to uploading files to be able to exploit the vulnerability, so if you have strict controls on this and trust all who have this permission, you're not affected.
Published May 15, 2024
Affected packages
ezsystems/ezpublish-legacy
- Ecosystem
- Composer (PHP)
- Affected
- >= 2019.3.0, < 2019.3.4.2
- Fixed in
- 2019.3.4.2
- Check
composer show ezsystems/ezpublish-legacy
ezsystems/ezpublish-legacy
- Ecosystem
- Composer (PHP)
- Affected
- >= 2017.12.0, < 2017.12.7.2
- Fixed in
- 2017.12.7.2
- Check
composer show ezsystems/ezpublish-legacy
ezsystems/ezpublish-legacy
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.4.0, < 5.4.14.1
- Fixed in
- 5.4.14.1
- Check
composer show ezsystems/ezpublish-legacy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
This Security Advisory is about a vulnerability in the way eZ Platform and eZ Publish Legacy handles file uploads, which can in the worst case lead to remote code execution (RCE), a very serious threat. An attacker would need access to uploading files to be able to exploit the vulnerability, so if you have strict controls on this and trust all who have this permission, you're not affected. On the basis of the tests we have made, we also believe the vulnerability cannot be exploited as long as our recommended vhost configuration is used. Here is the v2.5 recommendation for Nginx, as an example:
https://github.com/ezsystems/ezplatform/blob/2.5/doc/nginx/vhost.template#L31
This vhost template specifies that only the file app.php in the web root is executed, while vulnerable configurations allow execution of any php file. Apache is affected in the same way as Nginx, and is also protected by using the recommended configuration. The build-in webserver in PHP stays vulnerable, as it doesn't use this type of configuration (this webserver should only be used for development, never for production). We cannot be 100% certain our configuration is not vulnerable. We also do not know if all our users use the recommended configuration, so we send out this fix to be on the safe side.
The fix includes a blacklist feature for uploaded filenames, such as ".php". The file types on the blacklist cannot be uploaded. The blacklist is configurable. In eZ Platform you will find it as ezsettings.default.io.file_storage.file_type_blacklist in eZ/Bundle/EzPublishCoreBundle/Resources/config/default_settings.yml in vendors/ezsystems/ezpublish-kernel. In eZ Publish Legacy you will find it as FileExtensionBlackList in settings/file.ini. By default it blocks these file types: php, php3, phar, phpt, pht, phtml, pgif. The fix also inclues a new block against path traversal attacks, though this kind of attack was not reproducible in our tests.
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-38739
ezsystems/ezpublish-legacy has a SQL injection in dfscleanup
high7.1No fixMay 29, 2026GHSA-2vh3-cj9j-mcj5
eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error template
mediumMay 15, 2024GHSA-39j2-4p9j-5w4j
Ez Platform Object Injection in legacy shop module
mediumMay 15, 2024GHSA-82rv-45pc-v28w
eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilities
highMay 15, 2024GHSA-cc2j-92jq-wgjg
eZ Publish Information disclosure in backend content tree menu
highMay 15, 2024GHSA-p9mp-vq4v-v5m5
eZ Publish Legacy Passwordless login for LDAP users
highMay 15, 2024
