Summary
Any storage file can be downloaded from p.sh if full server path is known
The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.
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.24.1 or later; ezsystems/ezplatform to 1.13.6.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2RH5-JVGX-PGW3? GHSA-2RH5-JVGX-PGW3 is a high-severity security vulnerability in ezsystems/ezplatform (composer), affecting versions >= 2.0.0, <= 2.5.24. It is fixed in 2.5.24.1, 1.13.6.1.
- Which versions of ezsystems/ezplatform are affected by GHSA-2RH5-JVGX-PGW3? ezsystems/ezplatform (composer) versions >= 2.0.0, <= 2.5.24 is affected.
- Is there a fix for GHSA-2RH5-JVGX-PGW3? Yes. GHSA-2RH5-JVGX-PGW3 is fixed in 2.5.24.1, 1.13.6.1. Upgrade to this version or later.
- Is GHSA-2RH5-JVGX-PGW3 exploitable, and should I be worried? Whether GHSA-2RH5-JVGX-PGW3 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-2RH5-JVGX-PGW3 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-2RH5-JVGX-PGW3?
- Upgrade
ezsystems/ezplatformto 2.5.24.1 or later - Upgrade
ezsystems/ezplatformto 1.13.6.1 or later
- Upgrade