dbcve.org
Commerce B2bApplication · Adobe

CVE-2025-24422

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 · moderate confidence

Adobe Commerce versions prior to 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, and 2.4.4-p11 contain an Improper Access Control vulnerability. A low-privileged authenticated attacker can bypass security controls to gain unauthorized read access to sensitive data without any user interaction.

MitigationApply the vendor-released security patches for the affected versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, or 2.4.8-beta1 and later) and verify the access control restrictions function correctly.

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. Verify Adobe Commerce B2B module is installed
    Run the command to list installed modules: bin/magento module:status --format=json | grep -i B2B or check composer.json for magento/module-b2b-core
    Affected if The B2B module is present and enabled on the system
  2. Determine the installed Adobe Commerce B2B version
    Run: bin/magento module:status Magento_B2b or check the version in composer.lock under magento/module-b2b-core
    Affected if The version matches any of these: < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.0
  3. Confirm the base Adobe Commerce version
    Run: bin/magento --version or check the version in app/etc/config.php
    Affected if The version is prior to 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, or 2.4.4-p11 (combined with B2B being enabled)
  4. Identify if B2B features with access control are in use
    Review the configuration at Stores > Configuration > B2B Features in the admin panel or check the database table core_config_data for b2b_features_enabled settings
    Affected if B2B features such as company accounts, shared catalogs, or requisition lists are enabled and accessible to low-privileged users

The environment is affected if Adobe Commerce B2B module is installed and enabled with a version matching the affected list or a base Commerce version prior to the patched releases.

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-released security patches for the affected versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, or 2.4.8-beta1 and later) and verify the access control restrictions function correctly.

Recommended fix Moderate confidence

Commerce B2B extension version 1.3.6 or later (verify exact fixed version in Adobe security bulletin)

  1. 1. Review the Adobe Commerce B2B release notes on helpx.adobe.com for security patches related to CVE-2025-24422
  2. 2. Identify the fixed B2B extension version (typically 1.3.6 or later) that addresses this Improper Access Control vulnerability
  3. 3. Backup your current Adobe Commerce installation and database before performing any upgrade
  4. 4. Update the Commerce B2B extension to the fixed version via Composer: composer require magento/module-b2b:{"version"} --no-update
  5. 5. Run composer update to install the fixed version
  6. 6. Clear Magento caches: php bin/magento cache:flush
  7. 7. Run database migrations if required: php bin/magento setup:upgrade
  8. 8. Re-index if necessary: php bin/magento indexer:reindex
Caveat Review Adobe release notes for any breaking changes between your current B2B version and the fixed version; may require Magento core version compatibility checks

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

Fix this in Commerce B2b Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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