dbcve.org
CommerceApplication · Adobe

CVE-2024-45128

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Authorization vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and have a low impact on integrity and availability. 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

An Improper Authorization vulnerability in Adobe Commerce allows low-privileged authenticated users to bypass security measures, potentially compromising integrity and availability of the e-commerce platform.

MitigationApply Adobe's security patches for versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier to address 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: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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 the Adobe Commerce or Magento installation
    Check if the system runs Adobe Commerce or Magento by locating the composer.json file in the web root or checking the app/etc/env.php file for platform identification.
    Affected if The system is confirmed to be Adobe Commerce or Magento.
  2. Determine the installed Adobe Commerce version
    Run the command 'php bin/magento --version' from the web root directory, or inspect the composer.json file to read the 'version' field.
    Affected if The installed version matches any of these: 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, or is any version for 'all versions'.
  3. Determine if Adobe Commerce B2B is installed
    Run the command 'php bin/magento module:status Magento_B2b' or check composer.json for the presence of 'magento/module-b2b' package.
    Affected if Adobe Commerce B2B module is enabled and the installed B2B version matches 1.3.3, 1.3.4, 1.3.5, or 1.4.2.
  4. Determine the installed Magento version
    Run 'php bin/magento --version' or check the composer.json file in an Magento Open Source installation to identify the version.
    Affected if The system is Magento Open Source and the version matches 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, or is any version for 'all versions'.
  5. Review low-privileged user accounts
    Check the admin user management panel or query the admin_user table in the database to list all users with roles other than full administrative privileges.
    Affected if There exist user accounts with limited or custom roles that could potentially exploit an authorization bypass.

A user is affected if they run Adobe Commerce or Magento with a version matching the affected list, or any version if labeled as 'all versions', particularly when low-privileged authenticated users exist in the system.

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 Adobe's security patches for versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier to address the authorization bypass.

Recommended fix High confidence

Adobe Commerce 2.4.7-p2 (or latest 2.4.x release with security patch)

  1. 1. Identify your current Adobe Commerce/Magento version by checking the composer.json file or admin panel.
  2. 2. Determine if your version is in the affected list (2.4.4, 2.4.5, 2.4.6, 2.4.7 or earlier).
  3. 3. For Adobe Commerce 2.4.4.x users: Upgrade to 2.4.4-p10 or later.
  4. 4. For Adobe Commerce 2.4.5.x users: Upgrade to 2.4.5-p9 or later.
  5. 5. For Adobe Commerce 2.4.6.x users: Upgrade to 2.4.6-p7 or later.
  6. 6. For Adobe Commerce 2.4.7.x users: Upgrade to 2.4.7-p2 or later.
  7. 7. Run composer update to apply the new packages.
  8. 8. Clear the Magento cache and reindex after upgrade.
Caveat Security patch releases are backward-compatible; however, always test in staging environment first as with any upgrade

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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