dbcve.org
CommerceApplication · Adobe

CVE-2025-24427

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 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 write 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 contains an Improper Access Control vulnerability allowing low-privileged attackers to bypass security measures and gain unauthorized write access. The vulnerability affects versions 2.4.8-beta1 through 2.4.4-p11 and earlier, and exploitation requires no user interaction.

MitigationApply the vendor-supplied security patch or upgrade to a patched Adobe Commerce version. Verify access controls are functioning correctly after implementation.

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.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:< 2.4.4= 2.4.4= 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Check Adobe Commerce version
    Locate the composer.json file in the Magento root directory and examine the 'version' field under 'require' > 'magento/product-community-edition', or access the admin panel and navigate to System > Settings > About Magento to view the installed version.
    Affected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8, or is earlier than 2.4.4.
  2. Check Adobe Commerce B2B module version
    Locate the composer.json file in the Magento root directory and examine the 'version' field under 'require' > 'magento/module-b2b', or run the command 'php bin/magento module:status Magento_B2b' from the command line to confirm the module version.
    Affected if The B2B module version matches 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0, or is earlier than 1.3.3.
  3. Verify if B2B module is enabled
    Run the command 'php bin/magento module:status Magento_B2b' from the command line in the Magento root directory, or check the app/etc/config.php file for the entry 'Magento_B2b' set to '1'.
    Affected if The B2B module is installed and enabled (value is 1 in config.php or module status shows as enabled).
  4. Check Magento Open Source version if Commerce not in use
    Locate the composer.json file in the Magento root directory and examine the 'version' field under 'require' > 'magento/module-b2b', or check the admin panel version display if available.
    Affected if The installed Magento Open Source version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8, or is earlier than 2.4.4, and the B2B module is enabled.

A user is affected if they are running Adobe Commerce or Magento Open Source version 2.4.4 through 2.4.8 (or earlier than 2.4.4) with the B2B module enabled, or Adobe Commerce B2B version 1.3.3 through 1.5.0 (or earlier than 1.3.3).

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 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply the vendor-supplied security patch or upgrade to a patched Adobe Commerce version. Verify access controls are functioning correctly after implementation.

Recommended fix Moderate confidence

Adobe Commerce 2.4.7 or later (2.4.7-p4 recommended) / Adobe Commerce B2B 1.3.6 or later

  1. Review the Adobe Commerce Security Bulletin (APSB25-14) for this vulnerability
  2. Identify your current Adobe Commerce/Magento version using bin/magento --version or the admin panel
  3. For Adobe Commerce versions 2.4.4 through 2.4.6, apply the latest security patch: 2.4.4-p12, 2.4.5-p11, 2.4.6-p9, 2.4.7-p4, or upgrade to 2.4.7 or later
  4. For Adobe Commerce B2B versions 1.3.3 through 1.3.5, apply the corresponding patch or upgrade to a patched version
  5. Verify the patch was applied successfully by checking bin/magento --version after patching
  6. Test the security fix by confirming low-privileged user accounts cannot gain unauthorized write access
  7. Ensure the upgrade does not break existing customizations or extensions in your environment
Caveat Review Adobe Commerce upgrade guides for potential breaking changes between minor versions; 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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