dbcve.org
CommerceApplication · Adobe

CVE-2023-22247

HIGH · 7.5 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 2.4.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An XML Injection vulnerability in Adobe Commerce allows unauthenticated attackers to inject arbitrary URLs and read arbitrary files from the filesystem by exploiting improper XML parsing that does not disable external entity processing. The vulnerability requires no user interaction and can be exploited remotely.

MitigationUpgrade Adobe Commerce to version 2.4.4-p3/2.4.5-p2 or later. Additionally, ensure XML parsers are configured to disable external entity (XXE) processing as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5
Magento Open SourceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe Commerce or Magento Open Source version
    Run 'bin/magento --version' from the Magento root directory, or inspect the composer.json file for the 'version' field or the 'magento/product-community-edition' package version.
    Affected if The installed version is 2.4.4, 2.4.5, or any version earlier than 2.4.4 (e.g., 2.4.3, 2.4.2, etc.)
  2. Locate XML upload or parsing functionality
    Search the codebase for XML handling code, particularly endpoints that accept XML input. Look for usages of SimpleXML, DOMDocument, or XMLReader classes, and identify any controllers or API endpoints that process XML files or payloads.
    Affected if The application contains custom or third-party code that parses XML without disabling external entity processing.
  3. Inspect XML parser configuration for external entity settings
    Review PHP configuration files and XML parsing code to verify whether LIBXML_NOENT or LIBXML_DTDLOAD flags are used when loading XML, and confirm that external entity processing is explicitly disabled in the parser configuration.
    Affected if XML parsers are configured to allow external entity processing (XXE) rather than having it disabled.

You are affected if your installed Adobe Commerce or Magento Open Source version is 2.4.4, 2.4.5, or any version prior to 2.4.4, and your application processes XML with external entity processing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.4 or later
Fixed in 2.4.4
Interim mitigation

Upgrade Adobe Commerce to version 2.4.4-p3/2.4.5-p2 or later. Additionally, ensure XML parsers are configured to disable external entity (XXE) processing as a defense-in-depth measure.

Recommended fix Moderate confidence

2.4.4-p3+ or 2.4.5-p2+ (latest available patch version for your release line)

  1. 1. Backup your Magento database and files before proceeding with any upgrade or patch
  2. 2. Determine your current Adobe Commerce/Magento Open Source version by running: `php bin/magento --version`
  3. 3. For Magento 2.4.4: Upgrade to 2.4.4-p3 or later by running: `composer require-commerce magento/product-community-edition=2.4.4-p3 --no-update`
  4. 4. For Magento 2.4.5: Upgrade to 2.4.5-p2 or later by running: `composer require-commerce magento/product-community-edition=2.4.5-p2 --no-update`
  5. 5. After upgrading, clear the cache: `php bin/magento cache:flush`
  6. 6. Verify the upgrade was successful: `php bin/magento --version`
  7. 7. Re-index the catalog: `php bin/magento indexer:reindex`
  8. 8. Deploy static content if in production mode: `php bin/magento setup:static-content:deploy`
Caveat Patch upgrades are typically backward compatible but test in staging first; major version jumps may require code changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22247 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data