dbcve.org
Commerce B2bApplication · Adobe

CVE-2025-24424

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Improper Access Control vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read 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 that allows low-privileged authenticated users to bypass security mechanisms and gain unauthorized read access to sensitive data. The vulnerability affects multiple versions from 2.4.4-p11 and earlier through 2.4.8-beta1 and requires no user interaction to exploit.

MitigationApply the vendor-supplied security patches for the affected Adobe Commerce versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, 2.4.8-beta1). After patching, verify that access controls function correctly and no regression in authorized functionality occurs.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installation and version
    Run `bin/magento --version` or inspect `composer.json` to determine the installed Magento version
    Affected if Version is 2.4.4-p11 or earlier, 2.4.5-p10 or earlier, 2.4.6-p8 or earlier, 2.4.7-p3 or earlier, or 2.4.8-beta1
  2. Confirm Adobe Commerce B2b module is installed
    Run `bin/magento module:status` and look for Magento_Company or B2b-related modules, or inspect `composer.json` for magento/module-b2b
    Affected if B2b module is present in the enabled modules list
  3. Determine B2b module version
    Run `bin/magento module:status Magento_Company` or check the version in `composer.lock` under magento/module-b2b
    Affected if B2b version is less than 1.3.3, equals 1.3.3, equals 1.3.4, equals 1.3.5, equals 1.4.2, or equals 1.5.0
  4. Verify low-privileged user accounts exist
    Check the user management section in admin panel or query the admin_user table for accounts with limited roles
    Affected if There are authenticated user accounts with roles that should have restricted access to sensitive data
  5. Identify accessible API endpoints for low-privilege users
    Review REST API endpoints and GraphQL resolvers that accept authenticated sessions, particularly those related to company data, orders, or customer information
    Affected if Low-privilege users can access endpoints that should require higher permissions to read sensitive data

You are affected if you are running Adobe Commerce with the B2b module at a vulnerable version (1.3.3 through 1.5.0, or less than 1.3.3) and have low-privileged authenticated users who can potentially read sensitive data they should not access.

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 the vendor-supplied security patches for the affected Adobe Commerce versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, 2.4.8-beta1). After patching, verify that access controls function correctly and no regression in authorized functionality occurs.

Recommended fix High confidence

Adobe Commerce B2B extension version 1.3.6 or later / Adobe Commerce 2.4.4-p11 or later

  1. 1. Verify current Adobe Commerce B2B extension version by running: bin/magento --version and checking the B2B module version via composer or admin panel
  2. 2. Backup the current installation including database and files
  3. 3. Upgrade Adobe Commerce B2B extension to version 1.3.6 or later using composer: composer require magento/module-b2b:^1.3.6 --no-update
  4. 4. Run composer update to install the new version: composer update magento/module-b2b
  5. 5. Clear Magento cache: bin/magento cache:clean
  6. 6. Re-deploy static content if needed: bin/magento setup:static-content:deploy
  7. 7. Verify the upgrade was successful by checking the B2B module version
Caveat Review Adobe Commerce 2.4.4-p11 release notes for any breaking changes; minor version upgrades typically have low risk but test in staging first

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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-2025-24424 — 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-24424 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