dbcve.org
CommerceApplication · Adobe

CVE-2025-43585

HIGH · 8.2 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier are affected by an Improper Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized access leading to a limited impact to confidentiality and a high impact to 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 · high confidence

This is an Improper Authorization vulnerability in Adobe Commerce (Magento) that allows attackers to bypass security measures and gain unauthorized access. The vulnerability affects versions 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier. Exploitation requires no user interaction and results in high integrity impact with limited confidentiality impact.

MitigationApply the vendor-provided security patch for this authorization bypass vulnerability to all affected Adobe Commerce installations. Verify that custom authorization logic and third-party extensions remain functional after patching.

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.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2
MagentoCMS
Affected:= 2.4.5= 2.4.6= 2.4.7= 2.4.8

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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. Identify the Adobe Commerce or Magento version
    Run the command: php bin/magento --version or check the composer.json file in the Magento root directory for the version entry
    Affected if The installed version is 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13, or any earlier 2.4.x version, or if using B2B extensions version 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.2
  2. Confirm the product type
    Check if the installation includes Adobe Commerce B2B functionality by reviewing the installed modules via: php bin/magento module:status | grep -i b2b
    Affected if Adobe Commerce B2B versions 1.3.3 through 1.5.2 are installed alongside the core Adobe Commerce platform
  3. Verify network exposure of admin panel
    Review web server configuration and firewall rules to determine if the Magento admin panel (/admin or custom admin path) is accessible from untrusted networks
    Affected if The admin panel or any storefront endpoint handling authorization-sensitive operations is exposed to the internet without IP restrictions or VPN wrapping
  4. Review custom authorization logic
    Inspect any custom modules in app/code or third-party extensions in vendor/ for overrides of: \Magento\Framework\AuthorizationInterface or ACL XML files in etc/acl.xml
    Affected if Custom authorization extensions are in use that may interact with the vulnerable authorization bypass path

Your environment is affected if Adobe Commerce or Magento Open Source version 2.4.4 through 2.4.8 (or corresponding B2B versions) is installed and the admin panel or authorization-sensitive endpoints are network-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

Apply the vendor-provided security patch for this authorization bypass vulnerability to all affected Adobe Commerce installations. Verify that custom authorization logic and third-party extensions remain functional after patching.

Recommended fix High confidence

Adobe Commerce/Magento 2.4.8 (or apply security patch p13/p12/p10/p5 for versions 2.4.4/2.4.5/2.4.6/2.4.7 respectively)

  1. 1. Identify the current Adobe Commerce/Magento version by running: php bin/magento --version
  2. 2. For version 2.4.4: Upgrade to 2.4.4-p13 or migrate to 2.4.8
  3. 3. For version 2.4.5: Upgrade to 2.4.5-p12 or migrate to 2.4.8
  4. 4. For version 2.4.6: Upgrade to 2.4.6-p10 or migrate to 2.4.8
  5. 5. For version 2.4.7: Upgrade to 2.4.7-p5 or migrate to 2.4.8
  6. 6. For Commerce B2b versions: Apply the corresponding security patch bundle for your Adobe Commerce version
  7. 7. Before upgrading, backup the database and codebase: php bin/magento setup:backup --code --media
  8. 8. Clear composer cache and update: composer require magento/product-community-edition=2.4.8 --no-update
Caveat Major version upgrades may have breaking changes; review Adobe Commerce 2.4.8 release notes for compatibility with custom modules and extensions

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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