dbcve.org
CommerceApplication · Adobe

CVE-2025-49556

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 Incorrect Authorization vulnerability that could result in a security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploitation of this issue does not require user interaction, and scope is unchanged.

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

Incorrect Authorization vulnerability in Adobe Commerce allows an unauthenticated attacker to bypass security measures and gain unauthorized read access. Exploitation requires no user interaction and does not escalate privileges beyond the application's existing scope.

MitigationApply vendor security patches for Adobe Commerce when available; in the interim, implement WAF rules and network-level access controls to restrict unauthorized access to affected endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Adobe Commerce or Magento version
    Run the CLI command: php bin/magento --version OR check the composer.json file in the installation root for the 'version' or 'magento/product-community-edition' / 'magento/product-enterprise-edition' package version
    Affected if The installed version matches one listed in affected ranges: Adobe Commerce < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8; Adobe Magento < 2.4.5, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9; Adobe Commerce B2b < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.2, = 1.5.3
  2. Confirm B2B extension version if applicable
    Run: php bin/magento module:status Magento_Company OR check composer.json for 'magento/module-b2b' package version
    Affected if Commerce B2b extension version matches the affected B2b version ranges listed above
  3. Verify application is network accessible
    Confirm the Adobe Commerce/Magento web application is accessible from network locations. Test with: curl -I https://your-domain.com/ (or HTTP for non-SSL setups)
    Affected if The application is reachable over the network, allowing unauthenticated attackers to send requests to affected endpoints
  4. Check for recent unauthorized access indicators
    Review web server access logs and application logs for unusual read access patterns from unauthenticated IP addresses, focusing on endpoints that should require authentication
    Affected if Logs show unexpected unauthenticated read access to sensitive endpoints that should be protected

A user is affected if their Adobe Commerce, Commerce B2b, or Magento installation version falls within any of the affected version ranges AND the application is network-accessible to unauthenticated attackers.

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 vendor security patches for Adobe Commerce when available; in the interim, implement WAF rules and network-level access controls to restrict unauthorized access to affected endpoints.

Recommended fix High confidence

2.4.4-p14 (for 2.4.4 baseline), 2.4.5-p13 (for 2.4.5 baseline), 2.4.6-p11 (for 2.4.6 baseline), or latest 2.4.7-pX

  1. 1. Identify your current Adobe Commerce/Magento version by running: php bin/magento --version
  2. 2. For Magento 2.4.4: Upgrade to version 2.4.4-p14 or later by running: composer require magento/product-community-edition=2.4.4-p14 --no-update && composer update
  3. 3. For Magento 2.4.5: Upgrade to version 2.4.5-p13 or later by running: composer require magento/product-community-edition=2.4.5-p13 --no-update && composer update
  4. 4. For Magento 2.4.6: Upgrade to version 2.4.6-p11 or later by running: composer require magento/product-community-edition=2.4.6-p11 --no-update && composer update
  5. 5. For Magento 2.4.7: Upgrade to latest available version (2.4.7-p1 or later)
  6. 6. Clear the cache after upgrade: rm -rf var/cache/* var/page_cache/* generated/*
  7. 7. Run setup upgrade: php bin/magento setup:upgrade
  8. 8. Reindex: php bin/magento indexer:reindex
Caveat Standard Adobe Commerce upgrade considerations apply - test in staging environment first, review extension compatibility, and backup database before production upgrade

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

Fix this in Commerce Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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