dbcve.org
CommerceApplication · Adobe

CVE-2024-34109

HIGH · 7.2 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction, but admin privileges are required.

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 · moderate confidence

Adobe Commerce contains an improper input validation vulnerability that allows authenticated administrators to execute arbitrary code. The flaw exists in the admin panel where user-supplied input is not properly validated before processing, enabling remote code execution in the context of the current admin user.

MitigationApply the appropriate Adobe security patch or upgrade to a fixed version (2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 or later). Limit admin panel access to trusted users and monitor for suspicious admin activity.

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.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6
Commerce WebhooksApplication
Affected:>= 1.2.0, <= 1.4.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Determine Adobe Commerce or Magento installed version
    Run the CLI command: bin/magento --version or check composer.json for the magento/product-community-edition or magento/enterprise-edition version entry
    Affected if The installed version is 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, or 2.4.6
  2. Check Adobe Commerce Webhooks module version
    Run: bin/magento module:status AdobeCommerce_Webhooks or inspect the composer.lock file for adobe/commerce-webhooks version
    Affected if The webhooks module version is between 1.2.0 and 1.4.0 inclusive
  3. Verify admin panel access is enabled
    Check the app/etc/env.php file for backend configuration settings, or confirm the admin URL is accessible and admin user accounts exist in the admin_user database table
    Affected if Admin panel access is available and functional with valid administrator credentials
  4. Inspect admin configuration for webhooks or custom script endpoints
    Review the admin panel configuration at Stores > Settings > Configuration > Services > Webhooks (if available), and check the database table webhook for suspicious webhook definitions
    Affected if Webhooks are configured or custom endpoints that accept user input are present in the admin panel

You are affected if your installed Adobe Commerce/Magento version is 2.3.7 through 2.4.6 or your webhooks module is between 1.2.0 and 1.4.0 and you have an active admin panel that could accept maliciously crafted input.

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 a release after 1.4.0
Interim mitigation

Apply the appropriate Adobe security patch or upgrade to a fixed version (2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 or later). Limit admin panel access to trusted users and monitor for suspicious admin activity.

Recommended fix High confidence

Adobe Commerce 2.4.7-p1 or later (or latest 2.4.x stable release)

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. For Adobe Commerce 2.4.4: Upgrade to version 2.4.4-p8 or later (e.g., 2.4.5 or higher)
  3. 3. For Adobe Commerce 2.4.5: Upgrade to version 2.4.5-p7 or later (e.g., 2.4.6 or higher)
  4. 4. For Adobe Commerce 2.4.6: Upgrade to version 2.4.6-p5 or later (e.g., 2.4.7 or higher)
  5. 5. For Adobe Commerce 2.4.7: Upgrade to version 2.4.7-p1 or later when available
  6. 6. For Commerce Webhooks 1.2.0-1.4.0: Upgrade to version 1.4.1 or later
  7. 7. Apply the upgrade using Composer: composer require magento/product-community-edition=2.4.7-p1 --no-update && composer update
  8. 8. Run setup upgrade: bin/magento setup:upgrade
Caveat Minor patch upgrades typically have minimal breaking changes; test in staging environment before production deployment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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