dbcve.org
CommerceApplication · Adobe

CVE-2024-34104

HIGH · 8.2 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
91/100
Remediation priority · Urgent
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 Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized access, leading to both confidentiality and integrity impact. 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 Authorization vulnerability allowing attackers to bypass security measures and gain unauthorized access. The vulnerability affects versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier, with no user interaction required for exploitation.

MitigationApply the vendor-released security patch or upgrade to a patched Adobe Commerce version to remediate the authorization bypass.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 Adobe Commerce or Magento installation version
    Run 'bin/magento --version' from the Magento root directory, or check the version field in composer.json at the project root
    Affected if The 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 (Commerce) or 2.4.4 through 2.4.7 (Magento)
  2. Verify Adobe Commerce Webhooks module is installed
    Run 'bin/magento module:status | grep Magento_Webhooks' or check for the presence of vendor/magento/module-webhooks in the codebase
    Affected if The webhooks module is present on any affected Commerce version listed above
  3. Confirm webhooks module is enabled
    Run 'bin/magento module:status' and verify Magento_Webhooks is listed as enabled, or check app/etc/config.php for 'Magento_Webhooks' => 1
    Affected if Magento_Webhooks shows as enabled in the module status output or config.php

You are affected if your Adobe Commerce or Magento installation runs version 2.4.4 through 2.4.7 (or 2.3.7/2.4.0-2.4.6 for Commerce) AND the Adobe Commerce Webhooks module is 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 a release after 1.4.0
Interim mitigation

Apply the vendor-released security patch or upgrade to a patched Adobe Commerce version to remediate the authorization bypass.

Recommended fix Moderate confidence

2.4.4-p9 (or latest 2.4.x release), 2.4.5-p8 (or latest 2.4.x release), 2.4.6-p6 (or latest 2.4.x release), 2.4.7-p1 (or latest 2.4.x release)

  1. 1. Identify your current Adobe Commerce/Magento version using the admin panel (System > Configuration > General) or command line: bin/magento --version
  2. 2. For Magento/OpenSource versions 2.4.4.x: Upgrade to version 2.4.4-p9 or later
  3. 3. For Magento/OpenSource versions 2.4.5.x: Upgrade to version 2.4.5-p8 or later
  4. 4. For Magento/OpenSource versions 2.4.6.x: Upgrade to version 2.4.6-p6 or later
  5. 5. For Magento/OpenSource versions 2.4.7.x: Upgrade to version 2.4.7-p1 or later
  6. 6. For Adobe Commerce (Commerce) versions: Apply the corresponding security patch SUPEE-XXXXX or upgrade to the patched version as indicated in the Adobe security bulletin
  7. 7. Clear the Magento cache after upgrade: bin/magento cache:clean
  8. 8. Re-index all data: bin/magento indexer:reindex
Caveat Security patches typically have minimal breaking changes; however, test thoroughly in a 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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