dbcve.org
CommerceApplication · Adobe

CVE-2025-24425

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 a Business Logic Error vulnerability that could result in a security feature bypass. An attacker could exploit this vulnerability to circumvent intended security mechanisms by manipulating the logic of the application's operations causing limited data modification. 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 a business logic error that allows attackers to bypass intended security mechanisms, enabling limited unauthorized data modification without any user interaction. The vulnerability affects multiple versions of the Magento Commerce platform.

MitigationApply the vendor-supplied security patch for the affected Adobe Commerce version. Review and test any business logic changes to ensure the security bypass is properly remediated and no unintended data modifications can occur.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 or Magento installation version
    Run command 'php bin/magento --version' or check the admin panel under System > Information. For composer-based installs, examine composer.lock or composer.json for the 'magento/product-community-edition' or 'magento/product-enterprise-edition' version.
    Affected if The installed version is less than 2.4.4, or equals 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8.
  2. Check if Adobe Commerce B2B module is installed
    Run command 'php bin/magento module:status Magento_B2b' or check via composer: 'composer show magento/module-b2b --installed'. The B2B module is optional and only present in Adobe Commerce (Enterprise) installations.
    Affected if The B2B module is installed with version less than 1.3.3, or equals 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0.
  3. Verify the security patch application status
    Check for the presence of the vendor-supplied security patch in the codebase. Look for recently modified files in app/code or patches directory, or query the patch management system if one is in use. The patch for this CVE is typically deployed as a code-level fix.
    Affected if The vendor security patch for CVE-2025-24425 has not been applied to the installation.
  4. Review business logic authorization configurations
    Examine the application configuration files and module settings related to data modification endpoints. Focus on admin panel settings under Stores > Configuration that control authorization for data write operations. The vulnerability involves bypassing security mechanisms for unauthorized data modification.
    Affected if Default or misconfigured authorization settings allow the business logic bypass to succeed, enabling limited unauthorized data changes without authentication.

Your environment is affected if you are running any Adobe Commerce or Magento version 2.4.4 through 2.4.8 (or below 2.4.4), or have the B2B module installed in versions 1.3.3 through 1.5.0 (or below 1.3.3), and the vendor security patch for this CVE has not been 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
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 for the affected Adobe Commerce version. Review and test any business logic changes to ensure the security bypass is properly remediated and no unintended data modifications can occur.

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.7 (latest stable 2.4.x release)

  1. 1. Verify current Adobe Commerce version by running: bin/magento --version or checking composer.json
  2. 2. Create a full backup of the database and files before proceeding with any upgrade
  3. 3. Review and resolve any incompatible third-party extensions via composer before upgrading
  4. 4. Run the upgrade command: composer require magento/product-community-edition=2.4.7 --no-update
  5. 5. Update dependencies: composer update
  6. 6. Clear the cache: bin/magento cache:clean
  7. 7. Run the upgrade script: bin/magento setup:upgrade
  8. 8. Re-index all indexes: bin/magento indexer:reindex
Caveat Potential compatibility issues with custom themes/extensions; test thoroughly 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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