{"answers":{"affected":"2 open source packages ship an affected version, including ezsystems/ezplatform.","exploited":"There is no known exploitation of GHSA-45qm-j4m9-whv9 in the wild and no public exploit code.","fix":"Upgrade ezsystems/ezplatform to 2.5.4 or later.","what":"GHSA-45qm-j4m9-whv9 is a vulnerability in ezsystems/ezplatform, published on 15 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-45qm-j4m9-whv9 and fix it if it is affected.\n\nWhat it is: GHSA-45qm-j4m9-whv9 is a vulnerability in ezsystems/ezplatform, published on 15 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-45qm-j4m9-whv9 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ezsystems/ezplatform (Packagist): affected from 2.5.0; fixed in 2.5.4\n- ezsystems/ezplatform (Packagist): affected from 2.5.0; fixed in 2.5.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-45qm-j4m9-whv9/ (Markdown: https://insights.sbomify.com/GHSA-45qm-j4m9-whv9/index.md)","id":"GHSA-45qm-j4m9-whv9","markdown":"https://insights.sbomify.com/GHSA-45qm-j4m9-whv9/index.md","name":"GHSA-45qm-j4m9-whv9","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"eZ Platform CMS","requires_auth":"none","summary":"Attackers can perform CSRF attacks on the login form because CSRF protection is disabled by default, requiring manual configuration to enable.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.\n\nIf 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:\n```\nsecurity:\n    firewalls:\n        ezpublish_front:\n            form_login:\n                csrf_token_generator: security.csrf.token_manager\n```\nNB: In eZ Platform 3.0 this file has been moved to config/packages/security.yaml","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"eZ Platform CSRF token in login form is disabled by default","id":"GHSA-45qm-j4m9-whv9","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.5.4"],"introduced":["2.5.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":null,"source":"GHSA-45qm-j4m9-whv9"},{"ecosystem":"Packagist","fixed":["2.5.4"],"introduced":["2.5.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":"pkg:composer/ezsystems/ezplatform","source":"GHSA-45qm-j4m9-whv9"}],"products":null,"published":"2024-05-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can perform CSRF attacks on the login form because CSRF protection is disabled by default, requiring manual configuration to enable.","url":"https://insights.sbomify.com/GHSA-45qm-j4m9-whv9/"}