dbcve.org
CommerceApplication · Adobe

CVE-2024-34107

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
100/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 Access Control vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and view minor unauthorised information. 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 · moderate confidence

Adobe Commerce contains an Improper Access Control vulnerability allowing unauthenticated attackers to bypass security measures and view minor unauthorized information. The flaw exists in the access control implementation and can be exploited without any user interaction, making it particularly dangerous.

MitigationApply the appropriate Adobe Commerce security patch or upgrade to a patched version (2.4.7-p1, 2.4.6-p6, 2.4.5-p8, or 2.4.4-p9 or later) to address the improper access control vulnerability.

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
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. Check Adobe Commerce or Magento version
    Run 'php bin/magento --version' from the Magento root directory, or inspect the composer.json file for the 'magento/product-community-edition' or 'magento/enterprise-edition' version entry
    Affected if The installed version matches 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 for Magento/Commerce, or 2.4.4 through 2.4.7 for Adobe Magento branded versions
  2. Check Adobe Commerce Webhooks module version
    Run 'composer show magento/module-commerce-webhooks' or inspect composer.json for 'magento/module-commerce-webhooks' version
    Affected if The webhooks module version is between 1.2.0 and 1.4.0 inclusive (including 1.2.0 and 1.4.0)
  3. Verify webhooks module is installed and enabled
    Run 'php bin/magento module:status | grep -i webhooks' or check the app/etc/config.php file for 'Magento_CommerceWebhooks' entry showing as '1'
    Affected if The Commerce Webhooks module is present and enabled, combined with an affected version from steps 1 or 2

You are affected if your Adobe Commerce or Magento installation version is 2.3.7 through 2.4.6 or 2.4.7, or if the Commerce Webhooks module version is between 1.2.0 and 1.4.0, as this improper access control vulnerability allows unauthenticated information disclosure.

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 Commerce security patch or upgrade to a patched version (2.4.7-p1, 2.4.6-p6, 2.4.5-p8, or 2.4.4-p9 or later) to address the improper access control vulnerability.

Recommended fix Moderate 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 checking the admin panel or running: bin/magento --version
  2. 2. Back up your entire Magento installation including database before proceeding with any upgrade
  3. 3. For Adobe Commerce 2.4.4-2.4.7: Apply the official security patch provided by Adobe (refer to Adobe Security Bulletin APSB24-18 for patch file)
  4. 4. Alternatively, upgrade to Adobe Commerce 2.4.7-p1 or later which contains the security fix
  5. 5. For Commerce Webhooks 1.2.0-1.4.0: Upgrade to Commerce Webhooks version 1.4.1 or later
  6. 6. Clear Magento cache after upgrade: bin/magento cache:clean
  7. 7. Re-index all data: bin/magento indexer:reindex
  8. 8. Verify the upgrade was successful by checking the version and testing critical functionality
Caveat Standard Adobe Commerce upgrade risks apply - test thoroughly in staging environment first; custom extensions may require compatibility updates

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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