dbcve.org
Commerce B2bApplication · Adobe

CVE-2025-24407

HIGH · 7.1 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
77/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-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Incorrect Authorization vulnerability that could result in a security feature bypass. A low privileged attacker could exploit this vulnerability to perform actions with permissions that were not granted leading to both a High impact to confidentiality and Low 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

Adobe Commerce contains an Incorrect Authorization vulnerability allowing low-privileged authenticated users to bypass security controls and perform actions beyond their granted permissions. The vulnerability affects multiple versions (2.4.8-beta1 through 2.4.4-p11) and enables unauthorized access without user interaction, resulting in high confidentiality impact and low integrity impact.

MitigationApply vendor-supplied security patches for CVE-2025-24407 or upgrade to patched versions of Adobe Commerce (2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12 or later). Thoroughly test authorization controls 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
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 core version
    Run 'composer show magento/product-community-edition 2>&1' or check composer.lock, or log into admin panel and navigate to System > Tools > Web Setup Wizard > System Upgrade to view version
    Affected if Version falls within 2.4.8-beta1 through 2.4.4-p11 range (including 2.4.4-p11)
  2. Identify Adobe Commerce B2B module version
    Run 'composer show magento/module-b2b 2>&1' or check if B2B extension is listed in composer.lock under vendor/magento/module-b2b
    Affected if B2B module version is < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, or = 1.5.0
  3. Confirm B2B features are enabled
    Log into admin panel, navigate to Stores > Settings > Configuration > B2B Features, or check app/etc/config.php for 'Magento_B2b' module set to 1
    Affected if B2B features module is enabled (Magento_B2b = 1 in config.php)
  4. Review user roles and permissions configuration
    Log into admin panel, navigate to System > Permissions > User Roles. Check if any roles grant elevated permissions beyond what the assigned user actually needs
    Affected if Users with low-privileged roles (such as limited catalog access) exist in the system and may have access beyond their intended permissions

Your environment is affected if Adobe Commerce core version is between 2.4.4-p11 and 2.4.8-beta1 AND the B2B module is installed and enabled with a vulnerable B2B version.

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
Upgrade available Upgrade to 1.3.3 or later
Fixed in 1.3.3
Interim mitigation

Apply vendor-supplied security patches for CVE-2025-24407 or upgrade to patched versions of Adobe Commerce (2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12 or later). Thoroughly test authorization controls after patching.

Recommended fix Moderate confidence

Commerce B2b version 1.3.6 or later

  1. 1. Identify the current Adobe Commerce B2b version by checking composer.json or the admin panel.
  2. 2. Confirm the current version is 1.3.3, 1.3.4, or 1.3.5 (or any version before 1.3.6).
  3. 3. Review the Adobe Commerce upgrade documentation at helpx.adobe.com for proper upgrade procedures.
  4. 4. Create a full backup of the database and files before proceeding with the upgrade.
  5. 5. Update the composer.json to require Commerce B2b version 1.3.6 or later: run `composer require magento/b2b:^1.3.6 --no-update` or the appropriate version constraint.
  6. 6. Run `composer update` to fetch and install the new version.
  7. 7. After composer update completes, run the Magento upgrade commands: `bin/magento setup:upgrade` followed by `bin/magento cache:clean`.
  8. 8. Verify the new version is installed by checking the admin panel or running `bin/magento --version`.
Caveat Review Adobe Commerce release notes for any behavior changes between 1.3.x versions; minor version upgrades typically have low risk

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

Fix this in Commerce B2b Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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