Skip to content
Fencer Vulns
high 8.1

CVE-2025-49555 json

Adobe Commerce | Cross-Site Request Forgery (CSRF) (CWE-352)

published 2025-08-12 14 mo ago modified 2026-06-17 4 mo ago also GHSA-5777-jj7p-mpqw , EUVD-2025-24452

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

Summary

Adobe Commerce versions 2.4.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in privilege escalation. A high-privileged attacker could trick a victim into executing unintended actions on a web application where the victim is authenticated, potentially allowing unauthorized access or modification of sensitive data. Exploitation of this issue requires user interaction in that a victim must visit a malicious website or click on a crafted link. Scope is changed.

Patch / fix

  • packagist magento/community-edition 2.4.5-p14, 2.4.6-p12, 2.4.7-p7, 2.4.8-p2, 2.4.9-alpha2
  • adobe commerce 2.4.4
  • adobe commerce_b2b 1.3.3
  • adobe magento 2.4.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist magento/project-community-edition
<=2.0.2
no fix listed
packagist magento/community-edition
>=2.4.9-alpha1, <2.4.9-alpha2
>=2.4.8-beta1, <2.4.8-p2
>=2.4.7-beta1, <2.4.7-p7
>=2.4.6-p1, <2.4.6-p12
<2.4.5-p14
1 listed version
2.4.9-alpha2
2.4.8-p2
2.4.7-p7
2.4.6-p12
2.4.5-p14

Affected products

  • Adobe Adobe Commerce

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Vulns 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.