p PatchFirst

PatchFirst · Latest vulnerabilities

ezsystems/ezpublish-legacy vulnerabilities

Vulnerabilities published for ezsystems/ezpublish-legacy in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 11

  1. CVE-2026-38739

    High · CVSS 7.1No fix published

    ezsystems/ezpublish-legacy has a SQL injection in dfscleanup

    NB: All tags and branches in this repository are past their end of life, so the vulnerability will not be fixed. The advisory is posted on the request of the researcher, for the information of anyone who might still use this software. ### Impact There is a security vulnerability in eZ Publish Legacy, affecting the dfscleanup.php script and the `_getFileList` function of the `eZDFSFileHandlerMySQLiBackend` class (kernel/private/classes/clusterfilehandlers/dfsbackends/mysqli.php). The vulnerability allows an attacker with local shell access and sufficient privileges to run dfscleanup.php to perform a union-based SQL injection against the eZ Pu

    Published Updated
  2. GHSA-39j2-4p9j-5w4j

    Not ratedFix available

    Ez Platform Object Injection in legacy shop module

    This Security Advisory is about a vulnerability in the Legacy shop module. A backend editor could perform object injection in discount rules. This would require backend access and permission to edit discount rules. While object injection in itself is a serious vulnerability, the permission requirement means that normally only administrators would be able to exploit it, that's why it was classified as Medium severity.

    • Update to 2017.12.7.3
    • Update to 2019.3.5.1
    • Update to 5.4.14.2
    Published Updated
  3. GHSA-9895-26wr-4fgv

    Not ratedFix available

    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. 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

    • Update to 2017.12.7.2
    • Update to 2019.3.4.2
    • Update to 5.4.14.1
    Published Updated
  4. GHSA-pqjm-xcp8-wgmm

    Not ratedFix available

    Ez Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploads

    The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper. **1. WEB SERVER CONFIGURATION** The sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/ As an example, here is how you can

    • Update to 2017.12.4.3
    • Update to 2018.6.1.4
    • Update to 2018.9.1.3
    • Update to 5.3.12.6
    • Update to 5.4.12.3
    Published Updated
  5. GHSA-p9mp-vq4v-v5m5

    Not ratedFix available

    eZ Publish Legacy Passwordless login for LDAP users

    This security advisory fixes a vulnerability in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy. Installations that are using the legacy LDAP login handler or the TextFile login handler in combination with the standard legacy login handler, may in rare cases be vulnerable to a failure of the standard login handler to verify passwords correctly, allowing unauthorised access. If your installation has never used the LDAP or TextFile login handlers, or never used legacy login at all, then it is not affected. Still, we recommend installing the update, to be on the safe side. To install, use Co

    • Update to 2017.12.4.1
    • Update to 2018.6.1.2
    • Update to 2018.9.1.1
    • Update to 5.3.12.4
    • Update to 5.4.12.1
    Published Updated
  6. GHSA-2vh3-cj9j-mcj5

    Not ratedFix available

    eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error template

    This security advisory fixes a vulnerability in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy via the LegacyBridge. Installations where all modules are disabled may be vulnerable to XSS injection in the module name. This is a rare configuration, but we still recommend installing the update, which adds the necessary input washing. To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/ezpublish-legacy/commit/4697bff700e8cf95d5847ea19dad3479a77b02d9

    • Update to 2017.12.4.2
    • Update to 2018.6.1.3
    • Update to 2018.9.1.2
    • Update to 5.3.12.5
    • Update to 5.4.12.2
    Published Updated
  7. GHSA-82rv-45pc-v28w

    Not ratedFix available

    eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilities

    This security advisory fixes 4 separate vulnerabilities in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy by itself or via the LegacyBridge. First, it increases the randomness, and thus the security, of the pseudo-random bytes used to generate a hash for the "forgot password" feature. This protects accounts against being taken over through attacks trying to predict the hash. If the increased randomness is not available in your PHP installation, it will now log a warning. Second, it improves security of the information collector feature, by ensuring no collection emails will be sent from

    • Update to 2017.12.2.1
    • Update to 5.3.12.3
    • Update to 5.4.11.3
    Published Updated
  8. GHSA-cc2j-92jq-wgjg

    Not ratedFix available

    eZ Publish Information disclosure in backend content tree menu

    This security advisory fixes an information disclosure vulnerability in the legacy admin content tree menu. If a view has been disabled in site.ini [SiteAccessRules] Rules, and an attacker accesses the backend with the URL to this module, then the tree menu may be displayed. Since the tree menu may contain hidden items, this may lead to information disclosure. We recommend that you install this Security Update as soon as possible. To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/ezpublish-legacy/commit/a4a0470f8d80f012fe14e4f8ab11c7d14375986c

    • Update to 2017.8.1.1
    • Update to 5.3.12.2
    • Update to 5.4.10.1
    Published Updated
  9. GHSA-jpwx-ffjq-wr4w

    Not ratedFix available

    Content object state fetch functions open to SQL injection

    ### Impact This Security Update is about a vulnerability in eZ Publish Legacy. The content object state code could be vulnerable to SQL injection. There is no known exploit, but one might be possible. If you use Legacy in any way, we strongly recommend that you install this update as soon as possible. ### Patches The fix is distributed via Composer, see "Patched versions".

    • Update to 2017.12.7.4
    • Update to 2019.03.6.1
    Published Updated
  10. CVE-2020-10806

    Critical · CVSS 9.8EPSS 2.32%Fix available

    CVE-2020-10806

    eZ Publish Kernel before 5.4.14.1, 6.x before 6.13.6.2, and 7.x before 7.5.6.2 and eZ Publish Legacy before 5.4.14.1, 2017 before 2017.12.7.2, and 2019 before 2019.03.4.2 allow remote attackers to execute arbitrary code by uploading PHP code, unless the vhost configuration permits only app.php execution.

    • Update to 2017.12.7.2
    • Update to 2019.03.4.2
    • Update to 5.4.14.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →