eZ Platform Rules to disable executable access are ignored on Platform.sh (eZ Cloud)
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (ezsystems/ezplatform 2.5.4, 1.13.5.1, 1.7.9.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist ezsystems/ezplatform
- Affected
- >= 2.5.0, < 2.5.4>= 1.13.0, < 1.13.5.1>= 1.7.0, < 1.7.9.1
- Fixed in
- 2.5.4, 1.7.9.1, 1.13.5.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6xch-2vxx-5pvr lists affected ranges: Packagist ezsystems/ezplatform >=2.5.0 =1.13.0 =1.7.0 <1.7.9.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-6xch-2vxx-5pvr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-6xch-2vxx-5pvr Advisory: eZ Platform Rules to disable executable access are ignored on Platform.sh (eZ Cloud) IDs: GHSA-6xch-2vxx-5pvr Record: https://patchnext.com/advisories/ghsa-6xch-2vxx-5pvr (revision 1, source checked 26 Oct 2026, 14:24 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: ezsystems/ezplatform 2.5.4, 1.13.5.1, 1.7.9.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist ezsystems/ezplatform: affected >= 2.5.0, < 2.5.4; >= 1.13.0, < 1.13.5.1; >= 1.7.0, < 1.7.9.1; fixed in 2.5.4, 1.7.9.1, 1.13.5.1 ## Suggested inspection (read-only) - Packagist ezsystems/ezplatform: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on ezsystems/ezplatform. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-6xch-2vxx-5pvr (GitHub-reviewed advisory GHSA-6xch-2vxx-5pvr lists affected ranges: Packagist ezsystems/ezplatform >=2.5.0 =1.13.0 =1.7.0 <1.7.9.1) Commands are suggestions: review each one before running it.
Loading voting…