dbcve.org
CommerceApplication · Adobe

CVE-2025-54265

MEDIUM · 5.9 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Incorrect Authorization vulnerability. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploit depends on conditions beyond the attacker's control. 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-p15 through 2.4.9-alpha2 contain an Incorrect Authorization vulnerability that allows attackers to bypass security measures and gain unauthorized read access to sensitive data. The exploit depends on specific conditions beyond the attacker's control and requires no user interaction.

MitigationApply the relevant Adobe security patch or upgrade to a patched version of Adobe Commerce beyond the affected releases.

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.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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 installation
    Run the command bin/magento --version or check the composer.json file for the version declaration
    Affected if The installed version is Adobe Commerce or Magento 2.4.4 through 2.4.9 (including patch versions like p15 through alpha2)
  2. Confirm B2B module version if installed
    Check the version of the magento/module-b2b-core package via composer show magento/module-b2b-core or inspect composer.lock
    Affected if The B2B module version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3
  3. Verify the vulnerable component is accessible
    Review the application configuration to determine if the authorization module handling sensitive data read operations is enabled and exposed
    Affected if The authorization component is active and accessible without additional authentication barriers beyond standard login
  4. Check for existing security patches
    Inspect the app/etc/applied.patches.list file or check for recent security-related patches in the codebase
    Affected if No Adobe security patch for CVE-2025-54265 has been applied

The environment is affected if running an unpatched Adobe Commerce or Magento version between 2.4.4-p15 and 2.4.9-alpha2, or any of the listed B2B module versions, with the vulnerable authorization component active.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Adobe security patch or upgrade to a patched version of Adobe Commerce beyond the affected releases.

Recommended fix Moderate confidence

Upgrade to Adobe Commerce / Magento Open Source 2.4.10

  1. Verify current Adobe Commerce/Magento version by running: bin/magento --version or checking composer.json
  2. Review extension and custom code compatibility with version 2.4.10 in a staging environment
  3. Create a full backup of the database and file system
  4. Test the upgrade in a non-production environment first
  5. Run bin/magento maintenance:enable before upgrading in production
  6. Run composer require magento/product-community-edition=2.4.10 --no-update in the project root
  7. Run composer update to fetch the new version
  8. Run bin/magento setup:upgrade to apply database migrations
Caveat Review release notes for breaking changes between your current version and 2.4.10; custom extensions and third-party modules may require updates

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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