dbcve.org
CommerceApplication · Adobe

CVE-2025-43586

HIGH · 8.1 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 →
87/100
Remediation priority · High
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.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier are affected by an Improper Access Control vulnerability that could result in privilege escalation. A low privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized elevated access. 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

Adobe Commerce contains an Improper Access Control vulnerability allowing a low-privileged attacker to bypass security measures and gain unauthorized elevated access. The vulnerability affects multiple 2.4.x versions and exploitation requires no user interaction, making it particularly dangerous in authenticated attack scenarios.

MitigationApply the vendor-provided security patch or upgrade to a non-vulnerable version as specified in Adobe's security bulletin. Review user role permissions and implement additional access control monitoring until the patch is applied.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Adobe Commerce or Magento installation
    Run the command 'php bin/magento --version' from the web root directory to retrieve the exact installed version number.
    Affected if The version displayed is 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8.
  2. Check Adobe Commerce B2B module version
    Run 'php bin/magento module:status Magento_B2b' to determine if the B2B module is enabled, then check the version in composer.json or the module configuration file.
    Affected if The B2B module is enabled and the version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.2.
  3. Verify patch installation status
    Inspect the app/etc/config.php file for the presence of security-related patches, or check the composer.lock file for any security patch entries related to CVE-2025-43586.
    Affected if No security patch for CVE-2025-43586 is installed and the base version matches the affected versions listed.

You are affected if your Adobe Commerce or Magento installation runs version 2.4.4 through 2.4.8 (or B2B versions 1.3.3-1.3.5, 1.4.2, 1.5.2) without the corresponding 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-provided security patch or upgrade to a non-vulnerable version as specified in Adobe's security bulletin. Review user role permissions and implement additional access control monitoring until the patch is applied.

Recommended fix High confidence

Adobe Commerce 2.4.8 (or latest 2.4.x stable release)

  1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. Backup your database and files before applying any patches
  3. Download the corresponding security patch from helpx.adobe.com or the Adobe Commerce developer portal
  4. For Adobe Commerce 2.4.4: Apply patch CE-2.4.4-p13 or upgrade to 2.4.4-p13
  5. For Adobe Commerce 2.4.5: Apply patch CE-2.4.5-p12 or upgrade to 2.4.5-p12
  6. For Adobe Commerce 2.4.6: Apply patch CE-2.4.6-p10 or upgrade to 2.4.6-p10
  7. For Adobe Commerce 2.4.7: Apply patch CE-2.4.7-p5 or upgrade to 2.4.7-p5
  8. For Adobe Commerce 2.4.8: No patch needed (contains fix)
Caveat Patches are backward-compatible security fixes; test in 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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