Skip to content
Fencer Intel
medium 4.3

CVE-2024-20718 json

[Spain] CSRF to delete Requisition Lists at Adobe Commerce

published 2y ago modified 4mo ago also GHSA-hqgj-4396-hmxv , EUVD-2024-18433

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

Adobe Commerce versions 2.4.6-p3, 2.4.5-p5, 2.4.4-p6 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to trick a victim into performing actions they did not intend to do, which could be used to bypass security measures and gain unauthorized access. Exploitation of this issue requires user interaction, typically in the form of the victim clicking a link or visiting a malicious website.

Patch / fix

  • packagist magento/community-edition 2.4.4-p7, 2.4.5-p6, 2.4.6-p4

Is CVE-2024-20718 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
1 listed version
>=2.4.6-p1, <2.4.6-p4
>=2.4.5-p1, <2.4.5-p6
>=2.4.4-p1, <2.4.4-p7
2.4.6-p4
2.4.5-p6
2.4.4-p7
packagist magento/project-community-edition
<=2.0.2
no fix listed

Affected products

  • Adobe Adobe Commerce
  • adobe commerce

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.