dbcve.org
CommerceApplication · Adobe

CVE-2024-45115

CRITICAL · 9.8 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 →
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-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Authentication vulnerability that could result in privilege escalation. An attacker could exploit this vulnerability to gain unauthorized access or elevated privileges within the application. 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 authentication vulnerability allowing unauthorized attackers to bypass authentication mechanisms and escalate privileges to administrator levels. The flaw affects multiple supported versions (2.4.4-p10 through 2.4.7-p2) and can be exploited without any user interaction, making it highly exploitable in automated attacks.

MitigationApply the vendor-supplied security patches (Adobe Security Bulletin APSB24-18) to upgrade to versions 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, and 2.4.7-p3 or later. After patching, verify that authentication workflows function correctly and conduct privilege audits to confirm unauthorized elevated accounts do not exist.

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
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. Determine installed Adobe Commerce version
    Run the command 'php bin/magento --version' from the Magento root directory, or check the version.php file in app/Magento/ and the composer.json file
    Affected if The installed version is 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2 or earlier within the 2.4.4 through 2.4.7 release families, or matches any of the specific affected versions listed (2.3.7, 2.4.0 through 2.4.3, etc.)
  2. Confirm patch level
    Check the applied patches by reviewing the app/etc/config.php file or running 'bin/magento module:status' to verify if security patch APSB24-18 has been applied
    Affected if The system is running a version that predates patches 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3 and no corresponding security patch has been installed
  3. Audit administrator accounts for unauthorized creation
    Log into the admin panel and navigate to System > Permissions > All Users, or query the admin_user database table directly, to review all accounts with administrator privileges
    Affected if Any administrator account exists that was not created by known, authorized personnel, or if the total number of admin accounts exceeds expectations
  4. Review authentication logs for anomaly patterns
    Examine logs in var/log/ directory (especially authentication.log, exception.log, or webserver access logs) for failed authentication attempts followed by successful admin access from unfamiliar IP addresses or API token usage
    Affected if Logs show authentication bypass patterns such as successful admin access immediately after failed attempts, access from unexpected IP addresses, or API calls that bypassed normal login flows

The environment is affected if it runs any Adobe Commerce or Magento version from 2.4.4-p10 through 2.4.7-p2 (or older versions like 2.3.7 through 2.4.3) without the APSB24-18 security patch applied.

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 vendor-supplied security patches (Adobe Security Bulletin APSB24-18) to upgrade to versions 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, and 2.4.7-p3 or later. After patching, verify that authentication workflows function correctly and conduct privilege audits to confirm unauthorized elevated accounts do not exist.

Recommended fix High confidence

Upgrade to the latest patch for your release line: 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2 (or later)

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. Determine which release line you are on (2.4.4, 2.4.5, 2.4.6, or 2.4.7)
  3. 3. For 2.4.4.x users: Upgrade to version 2.4.4-p10 or later
  4. 4. For 2.4.5.x users: Upgrade to version 2.4.5-p9 or later
  5. 5. For 2.4.6.x users: Upgrade to version 2.4.6-p7 or later
  6. 6. For 2.4.7.x users: Upgrade to version 2.4.7-p2 or later
  7. 7. After upgrade, clear the cache: bin/magento cache:flush
  8. 8. Verify the upgrade was successful: bin/magento --version
Caveat Security patches typically have minimal risk; always test 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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