CVE-2024-39409

Magento Open Source versions 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could allow an attacker to bypass security features and perform minor unauthorised actions on behalf of a user. The vulnerability could be exploited by tricking a victim into clicking a link or loading a page that submits a malicious request. Exploitation of this issue requires user interaction.

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.

CVE-2024-39409 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-39409? CVE-2024-39409 is a medium-severity cross-site request forgery (CSRF) vulnerability in magento/community-edition (composer), affecting versions >= 2.4.7-p1, < 2.4.7-p2. It is fixed in 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2024-39409? CVE-2024-39409 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of magento/community-edition are affected by CVE-2024-39409? magento/community-edition (composer) versions >= 2.4.7-p1, < 2.4.7-p2 is affected.
4. Is there a fix for CVE-2024-39409? Yes. CVE-2024-39409 is fixed in 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10. Upgrade to this version or later.
5. Is CVE-2024-39409 exploitable, and should I be worried? Whether CVE-2024-39409 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
6. What actually determines whether CVE-2024-39409 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.
7. How do I fix CVE-2024-39409?
   • Upgrade magento/community-edition to 2.4.7-p2 or later
   • Upgrade magento/community-edition to 2.4.6-p7 or later
   • Upgrade magento/community-edition to 2.4.5-p9 or later
   • Upgrade magento/community-edition to 2.4.4-p10 or later