CVE-2025-49549 json
Adobe Commerce | Incorrect Authorization (CWE-863)
published 2025-06-25 16 mo ago modified 2026-06-17 4 mo ago also GHSA-85jx-x9r4-45m2 , EUVD-2025-19134
- cvss
- 2.7
- 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 33%
- public exploits
- 0
- none known
Summary
Adobe Commerce versions 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier are affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. A high-privileged attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized access. Exploitation of this issue does not require user interaction.
Patch / fix
- packagist magento/community-edition 2.4.5-p13, 2.4.6-p11, 2.4.7-p6
- adobe commerce_b2b 1.3.3
- adobe commerce 2.4.4
- adobe magento 2.4.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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.7-beta1, <2.4.7-p6 >=2.4.6-p1, <2.4.6-p11 <2.4.5-p13 1 listed version |
2.4.7-p6 2.4.6-p11 2.4.5-p13 |
Affected products
- Adobe Adobe Commerce
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
helpx.adobe.com
/security/products/magento/apsb25-50.html
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-49549
advisory
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2025-49549
- GitHub Advisory GHSA-85jx-x9r4-45m2
- NVD CVE-2025-49549
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.