dbcve.org
CommerceApplication · Adobe

CVE-2024-34106

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Incorrect Authorization vulnerability that could result in a security feature bypass. An attacker could exploit this vulnerability to gain unauthorized access or perform actions with the privileges of another user. 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 versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier contain an Incorrect Authorization vulnerability allowing security feature bypass. An unauthenticated attacker can exploit this to gain unauthorized access or perform actions with another user's privileges without any user interaction.

MitigationApply the official Adobe security patch or upgrade to a patched version of Adobe Commerce. Review and validate authorization controls after applying the fix.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 version
    Run `bin/magento --version` from the Magento root directory, or check the `composer.json` file for the `magento/product-community-edition` or `magento/enterprise-edition` version entry, or log into the admin panel and check System > Configuration > General > Advanced > Advanced for the version display.
    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, 2.4.6, or 2.4.7.
  2. Check if Adobe Commerce Webhooks module is installed
    Run `bin/magento module:status` and look for `Magento_Webhooks` in the output, or check the `app/etc/config.php` file for the presence of `Magento_Webhooks` set to '1', or run `composer show | grep magento/webhooks` to list the installed webhooks package.
    Affected if The webhooks module version is >= 1.2.0 and <= 1.4.0.
  3. Verify webhooks configuration
    Check the webhooks configuration file at `app/etc/config.php` or look for webhook-related configurations in the admin panel under Stores > Settings > Configuration > Services > Webhooks, if that menu exists in the installed version.
    Affected if Webhooks are enabled and configured.
  4. Review admin access logs for unauthorized actions
    Check the admin activity log table in the database (such as `admin_user` or `admin_action_log` tables if available) or review web server access logs for unexpected admin API calls or endpoint accesses from unauthenticated or unexpected IP addresses.
    Affected if There are admin actions performed by users without proper authentication tokens or from unexpected sessions.
  5. Check for unusual user privilege escalations
    Review the database tables `authorization_role` and `authorization_rule` to verify that user roles are correctly assigned, or examine the customer and admin user tables for any unauthorized modifications to user permissions or group assignments.
    Affected if Users have been assigned elevated privileges or are able to access resources outside their assigned role scope.

You are affected if you are running Adobe Commerce or Magento versions 2.3.7 through 2.4.7 with the webhooks module enabled (version 1.2.0-1.4.0), and you observe unauthorized access or privilege escalation in your environment.

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 official Adobe security patch or upgrade to a patched version of Adobe Commerce. Review and validate authorization controls after applying the fix.

Recommended fix Moderate confidence

Magento 2.4.7-p1 (or latest 2.4.x stable release)

  1. 1. Back up your current Magento/Adobe Commerce database and codebase
  2. 2. Review the Adobe Commerce upgrade documentation at helpx.adobe.com for your current version
  3. 3. Update Composer dependencies to target the fixed release (Magento 2.4.7-p1 or later for 2.4.x versions)
  4. 4. Run the upgrade command: composer require magento/product-community-edition=<version> --no-update
  5. 5. Clear caches: bin/magento cache:flush
  6. 6. Run database migrations if required: bin/magento setup:upgrade
  7. 7. Reindex: bin/magento indexer:reindex
  8. 8. Verify the patch is applied by checking the installed version matches the fixed release
Caveat Standard upgrade risks apply - test in staging environment first, particularly if using custom modules or themes

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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