Summary
Impact
File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this.
The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.
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.
Remediation advice
See "Patched versions".
Commit: https://github.com/ezsystems/ezplatform-kernel/commit/7e472317f7c75f45f72f74c38406952d8bea0de1
Frequently Asked Questions
- What is GHSA-MWVH-P3HX-X4GG? GHSA-MWVH-P3HX-X4GG is a medium-severity unrestricted upload of dangerous file types vulnerability in ezsystems/ezplatform-kernel (composer), affecting versions >= 1.3.0, < 1.3.35. It is fixed in 1.3.35. The application accepts file uploads without adequately restricting the file type or content.
- Which versions of ezsystems/ezplatform-kernel are affected by GHSA-MWVH-P3HX-X4GG? ezsystems/ezplatform-kernel (composer) versions >= 1.3.0, < 1.3.35 is affected.
- Is there a fix for GHSA-MWVH-P3HX-X4GG? Yes. GHSA-MWVH-P3HX-X4GG is fixed in 1.3.35. Upgrade to this version or later.
- Is GHSA-MWVH-P3HX-X4GG exploitable, and should I be worried? Whether GHSA-MWVH-P3HX-X4GG 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-MWVH-P3HX-X4GG 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-MWVH-P3HX-X4GG? Upgrade
ezsystems/ezplatform-kernelto 1.3.35 or later.