Summary
eZ Platform CSRF token in login form is disabled by default
his security advisory fixes a potential vulnerability in the eZ Platform log in form. That form has a Cross-Site Request Forgery (CSRF) token, but the CSRF functionality is not enabled by default, meaning the token is inactive. The fix is distributed via Composer as ezsystems/ezplatform v2.5.4, and in v3.0.0 when that will be released.
If you'd like to manually enable it in your configuration, this is done by editing your app/config/security.yml and setting the "csrf_token_generator" key to "security.csrf.token_manager", like this:
security:
firewalls:
ezpublish_front:
form_login:
csrf_token_generator: security.csrf.token_manager
NB: In eZ Platform 3.0 this file has been moved to config/packages/security.yaml
Impact
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
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
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-45QM-J4M9-WHV9? GHSA-45QM-J4M9-WHV9 is a high-severity cross-site request forgery (CSRF) vulnerability in ezsystems/ezplatform (composer), affecting versions >= 2.5.0, < 2.5.4. It is fixed in 2.5.4. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of ezsystems/ezplatform are affected by GHSA-45QM-J4M9-WHV9? ezsystems/ezplatform (composer) versions >= 2.5.0, < 2.5.4 is affected.
- Is there a fix for GHSA-45QM-J4M9-WHV9? Yes. GHSA-45QM-J4M9-WHV9 is fixed in 2.5.4. Upgrade to this version or later.
- Is GHSA-45QM-J4M9-WHV9 exploitable, and should I be worried? Whether GHSA-45QM-J4M9-WHV9 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-45QM-J4M9-WHV9 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-45QM-J4M9-WHV9? Upgrade
ezsystems/ezplatformto 2.5.4 or later.