Skip to content
Fencer Intel
critical 9.1

CVE-2025-24434 in the critical feed json

Adobe Commerce | Incorrect Authorization (CWE-863)

published last yr. modified 4mo ago also GHSA-fppq-f2m6-xv5c , EUVD-2025-3713

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

Summary

Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Incorrect Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized access. Exploitation of this issue does not require user interaction. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact as high.

Patch / fix

  • packagist magento/community-edition 2.4.4-p12, 2.4.5-p11, 2.4.6-p9, 2.4.7-p4, 2.4.8-beta2

Is CVE-2025-24434 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
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
>=2.4.8-beta1, <2.4.8-beta2
>=2.4.7-beta1, <2.4.7-p4
>=2.4.6-p1, <2.4.6-p9
>=2.4.5-p1, <2.4.5-p11
<2.4.4-p12
2.4.8-beta2
2.4.7-p4
2.4.6-p9
2.4.5-p11
2.4.4-p12
packagist magento/project-community-edition
<=2.0.2
no fix listed

Affected products

  • Adobe Adobe Commerce

Classification

Weakness

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.