Summary
eZ Platform Rules to disable executable access are ignored on Platform.sh (eZ Cloud)
The recommended Apache/Nginx virtual host configuration for eZ Platform includes a rewrite rule for blocking access to executable files in the var directory. This rule does not work when using eZ Platform Cloud (i.e. running eZ Platform on the Platform.sh cloud service).
The consequence of this is that in such a setup, those executable files may be downloadable. They will not be executable, unless you have specifically configured platform.sh to allow that (which you really should not do). The severity of the download access is limited, but it's better if the platform.sh cloud setup works the same way as regular eZ Platform does. All platform.sh setups are affected.
The fix adds a rule to the .platform.app.yaml configuration file, with the same effect as the rewrite rule already mentioned. After applying the fix, any attempt to access such files will fail with Access Denied. This security update is distributed via Composer as ezsystems/ezplatform 1.7.9.1, and 1.13.5.1, and 2.5.4. This is the commit: https://github.com/ezsystems/ezplatform/commit/773dddc0d8fe4fda34d2153a401eeaa6cc30b1ff
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
ezsystems/ezplatform to 2.5.4 or later; ezsystems/ezplatform to 1.13.5.1 or later; ezsystems/ezplatform to 1.7.9.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-6XCH-2VXX-5PVR? GHSA-6XCH-2VXX-5PVR is a medium-severity security vulnerability in ezsystems/ezplatform (composer), affecting versions >= 2.5.0, < 2.5.4. It is fixed in 2.5.4, 1.13.5.1, 1.7.9.1.
- Which versions of ezsystems/ezplatform are affected by GHSA-6XCH-2VXX-5PVR? ezsystems/ezplatform (composer) versions >= 2.5.0, < 2.5.4 is affected.
- Is there a fix for GHSA-6XCH-2VXX-5PVR? Yes. GHSA-6XCH-2VXX-5PVR is fixed in 2.5.4, 1.13.5.1, 1.7.9.1. Upgrade to this version or later.
- Is GHSA-6XCH-2VXX-5PVR exploitable, and should I be worried? Whether GHSA-6XCH-2VXX-5PVR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-6XCH-2VXX-5PVR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-6XCH-2VXX-5PVR?
- Upgrade
ezsystems/ezplatformto 2.5.4 or later - Upgrade
ezsystems/ezplatformto 1.13.5.1 or later - Upgrade
ezsystems/ezplatformto 1.7.9.1 or later
- Upgrade