CVE-2025-54267 json
Adobe Commerce | Incorrect Authorization (CWE-863)
published 2025-10-14 12 mo ago modified 2026-10-08 32 d ago also GHSA-qvwr-p3hj-j6jf , EUVD-2025-34459
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- 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 gain unauthorized access to elevated privileges that increase integrity impact to high. 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.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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-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 |
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-54267
advisory
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2025-54267
- GitHub Advisory GHSA-qvwr-p3hj-j6jf
- NVD CVE-2025-54267
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.