dbcve.org
CommerceApplication · Adobe

CVE-2024-45148

HIGH · 8.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 →
94/100
Remediation priority · Urgent
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 Authentication vulnerability that could result in a security feature bypass. A low-privileged attacker could leverage this vulnerability to gain unauthorized access without proper credentials. 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 that allows a security feature bypass. Low-privileged attackers can gain unauthorized access to the application without proper credentials, and no user interaction is required for exploitation.

MitigationUpdate Adobe Commerce to the latest patched version beyond 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 as provided by Adobe's official security advisories.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Adobe Commerce or Magento installation version
    Run the command `php bin/magento --version` from the Adobe Commerce/Magento root directory, or inspect the `composer.json` file for the `version` field
    Affected if The installed version is any version prior to 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10, or matches 2.3.7, 2.4.0-2.4.7, or falls within the 'all versions' range without a security patch applied
  2. Confirm Adobe Commerce B2B extension version if used
    Run `php bin/magento module:status` to list enabled modules and check for B2B-related modules, or review `composer.json` for `magento/module-b2b` version
    Affected if The B2B extension version is 1.3.3, 1.3.4, 1.3.5, or 1.4.2 without corresponding security patches applied
  3. Review admin panel access controls
    Navigate to Stores > Settings > Configuration > Advanced > Admin in the admin dashboard, or inspect the `app/etc/env.php` file for admin URL and authentication settings
    Affected if The admin panel or related API endpoints are accessible without additional authentication layers or IP restrictions beyond default Magento authentication
  4. Audit exposed API endpoints
    Inspect `app/etc/webapi.xml` or check the `/rest/` and `/soap/` endpoint directories, and review `nginx.conf` or `.htaccess` for proxy configurations that may expose these endpoints
    Affected if REST or SOAP API endpoints are accessible externally without require_http_types or authentication token validation configured

The environment is affected if running any unpatched Adobe Commerce, Adobe Commerce B2B, or Magento version, particularly where admin or API endpoints are externally accessible.

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

Update Adobe Commerce to the latest patched version beyond 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, or 2.4.4-p10 as provided by Adobe's official security advisories.

Recommended fix High confidence

Apply security patch for your current version line: 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2

  1. 1. Identify current Adobe Commerce/Magento version by checking the composer.json file or running: bin/magento --version
  2. 2. Navigate to the Adobe Security Bulletin for this CVE at helpx.adobe.com/security bulleting
  3. 3. Download the appropriate security patch for your installed version (2.4.4-p10, 2.4.5-p9, 2.4.6-p7, or 2.4.7-p2)
  4. 4. Apply the patch following Adobe's standard patch application process: composer install, then apply the patch file
  5. 5. Clear the Magento cache: bin/magento cache:clean
  6. 6. Verify the patch was applied successfully by checking the version again
  7. 7. Test critical authentication flows to confirm the vulnerability is remediated
Caveat Patches are cumulative and should not introduce breaking changes; however, test in a staging environment first

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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