dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Aug 2024.
CommerceApplication · Adobe

CVE-2024-34102

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability that could result in arbitrary code execution. An attacker could exploit this vulnerability by sending a crafted XML document that references external entities. 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

Adobe Commerce contains an Improper Restriction of XML External Entity Reference (XXE) vulnerability in versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier. Attackers can exploit this by sending crafted XML documents that reference external entities, leading to arbitrary code execution without requiring any user interaction.

MitigationApply Adobe's official security patches for this vulnerability or upgrade to a patched version of Adobe Commerce (2.4.7-p1 or later). Review XML processing endpoints and disable external entity resolution as an additional hardening 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.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
Commerce WebhooksApplication
Affected:>= 1.2.0, < 1.5.0
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7

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
High
Availability
High

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

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 Adobe Commerce or Magento installed version
    Run the CLI command 'php bin/magento --version' or check the composer.json file in the Magento root directory for the version entry
    Affected if The installed version matches 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7
  2. Identify Adobe Commerce Webhooks module version
    Run 'composer show magento/module-webhooks' or check the composer.lock file for the installed version of the webhooks module
    Affected if The module version is >= 1.2.0 and < 1.5.0, or the module is present on an affected Adobe Commerce installation
  3. Verify if XML input processing is enabled
    Review the web server configuration and application routing to determine if endpoints that accept XML data are accessible (common paths include /webhooks, /api, or custom XML import endpoints)
    Affected if The application accepts XML input through any exposed API or webhook endpoints without XML external entity processing being explicitly disabled
  4. Check XML parser configuration
    Inspect php.ini settings for 'libxml_disable_entity_loader' or review custom XML parser configurations in the codebase that handle XML processing
    Affected if The XML parser configuration allows external entity loading or has not been explicitly hardened to disable external entities

You are affected if your Adobe Commerce or Magento version is 2.4.2 through 2.4.7 (or the specific versions listed) and the system processes XML input through webhooks or other endpoints without external entity protection 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 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Apply Adobe's official security patches for this vulnerability or upgrade to a patched version of Adobe Commerce (2.4.7-p1 or later). Review XML processing endpoints and disable external entity resolution as an additional hardening measure.

Recommended fix High confidence

Upgrade to 2.4.7 (latest stable) or apply latest security patches: 2.4.4-p8, 2.4.5-p7, 2.4.6-p5

  1. 1. Identify the currently installed Adobe Commerce or Magento version by checking the admin panel or composer.json
  2. 2. For Magento/Commerce 2.4.4: Upgrade to patch level 2.4.4-p8 or migrate to 2.4.7
  3. 3. For Magento/Commerce 2.4.5: Upgrade to patch level 2.4.5-p7 or migrate to 2.4.7
  4. 4. For Magento/Commerce 2.4.6: Upgrade to patch level 2.4.6-p5 or migrate to 2.4.7
  5. 5. For Magento/Commerce 2.4.7: Ensure running the base 2.4.7 release (no patch needed)
  6. 6. For Commerce Webhooks extension (if installed): Upgrade to version 1.5.0 or later
  7. 7. Back up the database and filesystem before applying the upgrade
  8. 8. Run composer update to pull the new versions: composer require magento/product-community-edition=2.4.7 --no-update (adjust version based on your target)
Caveat Security patches are backward compatible; however, always test in a staging environment before production deployment as minor behavioral changes may occur

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

Fix this in Commerce Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34102 — 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-2024-34102 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