dbcve.org
CommerceApplication · Adobe

CVE-2025-49554

HIGH · 7.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
See remediation →
84/100
Remediation priority · High
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.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by an Improper Input Validation vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability by providing specially crafted input, causing the application to crash or become unresponsive. 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 input validation vulnerability in multiple versions (2.4.4-p14 through 2.4.9-alpha1). Attackers can exploit this by sending specially crafted input that causes the application to crash or become unresponsive, resulting in denial of service. No user interaction is required for exploitation.

MitigationApply the vendor-supplied patch or update Adobe Commerce to a version beyond the affected releases (2.4.4-p14, 2.4.5-p13, 2.4.6-p11, 2.4.7-p6, 2.4.8-p1, 2.4.9-alpha1). Review input validation routines in custom modules as a secondary hardening measure.

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.2= 1.5.3
MagentoCMS
Affected:< 2.4.5= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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
    Run the command: bin/magento --version or check the composer.json file for the magento/product-community-edition or magento/enterprise-edition version entry
    Affected if The version shown matches any of these: 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or any version lower than 2.4.4 (for Commerce) or lower than 2.4.5 (for Magento open source)
  2. Check for patch version on Adobe Commerce 2.4.4
    If base version is 2.4.4, examine composer.lock or the setup:system-info output for the exact patch version (for example, 2.4.4-p13 or earlier is affected; 2.4.4-p14 and later are fixed)
    Affected if The installed patch version is p13 or earlier, or no patch version is shown and base version is 2.4.4
  3. Check for patch versions on Adobe Commerce 2.4.5 through 2.4.8
    For each of versions 2.4.5, 2.4.6, 2.4.7, 2.4.8, check the composer.lock or bin/magento --version output for the specific patch level
    Affected if The installed patch version is p12 or earlier for 2.4.5, p10 or earlier for 2.4.6, p5 or earlier for 2.4.7, or p0 (no patch) for 2.4.8
  4. Verify Adobe Commerce B2B extension version
    Check composer.json or composer.lock for the magento/module-b2b-core version, or run: composer show magento/module-b2b-core
    Affected if The B2B extension version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3, or any version lower than 1.3.3

You are affected if your Adobe Commerce or Magento installation version matches any of the specific versions listed (2.4.4 through 2.4.8 or older) and is not patched to the fixed patch levels (p14 for 2.4.4, p13 for 2.4.5, p11 for 2.4.6, p6 for 2.4.7, p1 for 2.4.8), or if your B2B extension is on an affected 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 / 2.4.4 / 2.4.5 or later
Fixed in 1.3.32.4.42.4.5
Interim mitigation

Apply the vendor-supplied patch or update Adobe Commerce to a version beyond the affected releases (2.4.4-p14, 2.4.5-p13, 2.4.6-p11, 2.4.7-p6, 2.4.8-p1, 2.4.9-alpha1). Review input validation routines in custom modules as a secondary hardening measure.

Recommended fix High confidence

Adobe Commerce/Magento 2.4.8 or later; Commerce B2B 1.3.7 or later

  1. 1. Identify your current Adobe Commerce/Magento installation version using the admin panel or command line: bin/magento --version
  2. 2. For Adobe Commerce (all editions): Upgrade to version 2.4.8 or later, which contains the fix for this Improper Input Validation vulnerability
  3. 3. For Adobe Commerce B2B: Upgrade to version 1.3.7 or later
  4. 4. For Magento Open Source: Upgrade to version 2.4.8 or later
  5. 5. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with custom extensions and themes
  6. 6. Create a full backup of the database and filesystem before performing the upgrade
  7. 7. Run the upgrade using Composer: composer require magento/product-community-edition=2.4.8 --no-update, then composer update
  8. 8. After upgrade, clear caches: bin/magento cache:flush
Caveat Standard Magento upgrade risks apply - review release notes for breaking changes, test all custom extensions and third-party integrations thoroughly in staging 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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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