dbcve.org
CommerceApplication · Adobe

CVE-2024-45124

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 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 have a low impact on integrity. 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 that allows attackers to bypass security measures without user interaction. The issue affects versions 2.4.4-p10 and earlier through 2.4.7-p2, enabling security feature bypass with low impact on integrity.

MitigationApply the relevant security patches or upgrade to Adobe Commerce versions beyond 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, and 2.4.4-p10 as specified in Adobe's official security bulletin.

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:all versions= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2
MagentoCMS
Affected:all versions= 2.4.3= 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. Determine the Adobe Commerce version
    Run the command 'php bin/magento --version' or check the composer.json file in the Adobe Commerce root directory for the magento/product-community-edition version
    Affected if The installed version is 2.4.4-p10 or earlier, or between 2.4.5 and 2.4.7-p2 (inclusive)
  2. Confirm Adobe Commerce B2B extension version if installed
    Run 'php bin/magento module:status' to list modules, or check composer.json for magento/module-b2b-core version
    Affected if The B2B extension version is 1.3.3, 1.3.4, 1.3.5, or 1.4.2
  3. Determine Adobe Magento version if using Magento Open Source
    Check composer.json or run 'php bin/magento --version' to identify if the installation is Magento Open Source rather than Adobe Commerce
    Affected if The installation is Magento Open Source version 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7
  4. Identify if the instance has external access
    Review network configuration and firewall rules to determine if the Adobe Commerce instance is accessible from external networks or the internet
    Affected if The instance is externally accessible and the version falls within the affected ranges listed above

A user is affected if their Adobe Commerce or Magento installation version is within 2.4.4-p10 and earlier through 2.4.7-p2 (or matches the specific B2B versions listed), and the instance processes requests from untrusted networks where the security bypass could be exploited.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant security patches or upgrade to Adobe Commerce versions beyond 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, and 2.4.4-p10 as specified in Adobe's official security bulletin.

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.4-p11 / 2.4.5-p10 / 2.4.6-p8 / 2.4.7-p3 or later, or Magento Open Source equivalents

  1. 1. Identify your current Adobe Commerce (Magento) version by checking composer.json or the admin panel footer.
  2. 2. For Adobe Commerce installations: upgrade to one of the patched releases: 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3 or later.
  3. 3. For Magento Open Source: upgrade to 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3 or later.
  4. 4. For Commerce B2B: ensure compatibility with the chosen Adobe Commerce version.
  5. 5. Before upgrading in production, test the upgrade in a staging environment.
  6. 6. Create a full backup of the database and codebase.
  7. 7. Run composer require magento/product-community-edition (or enterprise edition) with the target version, e.g., composer require magento/product-community-edition=2.4.7-p3 --no-update.
  8. 8. Run composer update to pull the new packages.
Caveat Patch releases are generally safe; however, test custom extensions and third-party modules for compatibility 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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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