CVE-2025-54263 json
Adobe Commerce | Incorrect Authorization (CWE-863)
published 2025-10-14 12 mo ago modified 2026-10-08 31 d ago also GHSA-69x9-xp2j-w8g8 , EUVD-2025-34461
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Incorrect Authorization vulnerability. A low-privileged attacker could leverage this vulnerability to bypass security measures and maintain unauthorized access. Exploitation of this issue does not require user interaction.
Patch / fix
- packagist magento/community-edition 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 12 mo ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% 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:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.4.9-alpha1, <2.4.9-alpha3 >=2.4.8-beta1, <2.4.8-p3 >=2.4.7-beta1, <2.4.7-p8 <2.4.6-p13 1 listed version |
2.4.9-alpha3 2.4.8-p3 2.4.7-p8 2.4.6-p13 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
Affected products
- Adobe Adobe Commerce
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
helpx.adobe.com
/security/products/magento/apsb25-94.html
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-54263
advisory
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2025-54263
- GitHub Advisory GHSA-69x9-xp2j-w8g8
- NVD CVE-2025-54263
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.