dbcve.org
CommerceApplication · Adobe

CVE-2025-49558

MEDIUM · 5.9 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 →
68/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.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 a Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability that could result in a security feature bypass. An attacker could exploit this vulnerability by manipulating the timing between the check of a resource's state and its use, allowing 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 versions 2.4.4-p14 through 2.4.9-alpha1 contain a Time-of-check Time-of-use (TOCTOU) race condition that enables security feature bypass. Attackers can manipulate the timing window between state validation and resource usage to achieve unauthorized write access without user interaction.

MitigationApply the vendor patch when released by Adobe. In the interim, review access controls and implement additional validation on sensitive write operations that may be vulnerable to timing manipulation.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify installed Adobe Commerce version
    Run the command: php bin/magento --version or check the composer.json file for the magento/product-community-edition version
    Affected if The version is 2.4.4-p14 or higher but lower than 2.4.9 (including 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9-alpha01)
  2. Identify installed Adobe Commerce B2B version
    Check composer.json for magento/module-b2b or run: php bin/magento module:status Magento_B2b
    Affected if The 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 on a vulnerable Commerce base
  3. Identify installed Adobe Magento version
    Check composer.json for magento/product-magento-base or the version file: var/cmrectory.txt or app/etc/env.php for version metadata
    Affected if The version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (including any patch versions within these releases)
  4. Confirm B2B module is enabled
    Run: php bin/magento module:status | grep -i b2b, then check if B2B features such as company accounts or shared catalogs are configured
    Affected if The Adobe Commerce B2B module is enabled on a vulnerable Commerce version, as the race condition affects B2B write operations

The environment is affected if Adobe Commerce, Adobe Commerce B2B, or Adobe Magento is running any version from 2.4.4-p14 through 2.4.9-alpha01, or matching the specific B2B versions listed, with B2B functionality enabled.

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 patch when released by Adobe. In the interim, review access controls and implement additional validation on sensitive write operations that may be vulnerable to timing manipulation.

Recommended fix Moderate confidence

Upgrade to the latest available Adobe Commerce/Magento 2.4.x release that includes the security patch for CVE-2025-49558 (consult Adobe Security Bulletin for exact version numbers)

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. Review the Adobe Security Bulletin (helpx.adobe.com) for CVE-2025-49558 to identify the specific patched version for your release line
  3. 3. Plan the upgrade: for Magento 2.4.4-p14 and earlier, upgrade to a patched version (2.4.4-p15+ or 2.4.5-p14+, 2.4.6-p12+, 2.4.7-p7+, or 2.4.8-p2+, 2.4.9+)
  4. 4. For Commerce B2b: ensure you upgrade to Commerce B2B version 1.3.3-p4 or later that includes the security patch
  5. 5. Back up your database and codebase before upgrading
  6. 6. Run the upgrade using Composer: composer require magento/product-community-edition=<version> --no-update, then composer update
  7. 7. Clear caches: rm -rf var/cache var/page_cache generated/code
  8. 8. Run setup upgrade: bin/magento setup:upgrade
Caveat Review Adobe's release notes for breaking changes between your current version and target version; major upgrades may require compatibility testing and PHP version updates

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

Fix this in Commerce Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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