CVE-2023-22247 json
Adobe Commerce XML Injection Arbitrary file system read
published 2023-03-27 3 y ago modified 2026-06-17 4 mo ago also GHSA-2444-8gj8-6fmx , EUVD-2023-26411
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Adobe Commerce versions 2.4.4-p2 (and earlier) and 2.4.5-p1 (and earlier) are affected by an XML Injection vulnerability that could lead to arbitrary file system read. An unauthenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.
Patch / fix
- packagist magento/community-edition 2.4.4-p3, 2.4.5-p2
- adobe commerce 2.4.4
- adobe magento_open_source 2.4.4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.4.5-p1, <2.4.5-p2 1 listed version >=2.4.4-p1, <2.4.4-p3 |
2.4.5-p2 2.4.4-p3 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
Affected products
- Adobe Magento Commerce
Classification
- Weakness
-
- CWE-91 XML Injection
References
-
helpx.adobe.com
/security/products/magento/apsb23-17.html
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-22247
advisory
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2023-22247
- GitHub Advisory GHSA-2444-8gj8-6fmx
- NVD CVE-2023-22247
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.