Read the docs
TI-2024-38637 Aliases GHSA-45qm-j4m9-whv9

eZ Platform CSRF token in login form is disabled by default

Priority LOW 38CWE-352Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Tampering
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-352.

Summary

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

Why it matters now

Fix Fixed ezsystems/ezplatform (Packagist): 2.5.4

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—ezsystems/ezplatform (Packagist)2.5.0 to before 2.5.42.5.4Patch availableGHSA-45qm-j4m9-whv9
  • ezsystems/ezplatform (Packagist) Vendor— Affected 2.5.0 to before 2.5.4 Fixed in 2.5.4 Patch available GHSA-45qm-j4m9-whv9

Remediation

  • Fix · GHSA-45qm-j4m9-whv9 ezsystems/ezplatform (Packagist) Fixed in 2.5.4 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-45qm-j4m9-whv9

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences