dbcve.org
CommerceApplication · Adobe

CVE-2025-54267

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access to elevated privileges that increase integrity impact to high. 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

This is an Incorrect Authorization vulnerability in Adobe Commerce affecting multiple versions (2.4.4-p15 through 2.4.9-alpha2). A low-privileged attacker can bypass existing security measures to gain unauthorized access to elevated privileges, with a high impact on system integrity. No user interaction is required for exploitation.

MitigationApply the Adobe security patch for CVE-2025-54267 or upgrade to a patched Adobe Commerce version as specified in Adobe's official security bulletin.

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

CVSS:3.1/AV:N/AC:L/PR:L/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
    Locate the app/etc/env.php file or check the composer.json file in the Magento root directory to find the installed version number. Alternatively, run the CLI command 'php bin/magento --version' if CLI access is available.
    Affected if The version displayed matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (including their specific patch releases such as 2.4.4-p15 through 2.4.9-alpha2)
  2. Confirm Adobe Commerce B2B extension version
    If the Adobe Commerce B2B extension is installed, check the composer.json or the B2B extension configuration file for the installed version number.
    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
  3. Verify Magento Open Source version
    If using Magento Open Source rather than Adobe Commerce, check the composer.json or run 'php bin/magento --version' to confirm the exact installation version.
    Affected if The version is 2.4.6, 2.4.7, 2.4.8, or 2.4.9

If your Adobe Commerce, Adobe Commerce B2B, or Magento installation matches any of the specific version numbers listed in the affected products range (2.4.4 through 2.4.9 or the corresponding B2B versions), your environment is potentially affected by this authorization bypass vulnerability.

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 Adobe security patch for CVE-2025-54267 or upgrade to a patched Adobe Commerce version as specified in Adobe's official security bulletin.

Recommended fix High confidence

Upgrade to the latest stable release (2.4.7-p8+, 2.4.8-p3+, or 2.4.9 stable) based on your current branch - for 2.4.4-p15 upgrade to 2.4.4-p16 or latest 2.4.x; for 2.4.5-p14 upgrade to 2.4.5-p15 or latest 2.4.x; for 2.4.6-p12 upgrade to 2.4.6-p13 or latest 2.4.x; for 2.4.7-p7 upgrade to 2.4.7-p8 or

  1. Identify your current Adobe Commerce/Magento version by checking the admin panel or composer.json
  2. Backup your entire codebase and database before proceeding
  3. Run composer require magento/product-community-edition:<version> --no-update for your target version
  4. Update composer: composer update
  5. Run bin/magento setup:upgrade to apply database migrations
  6. Clear caches: bin/magento cache:flush
  7. Verify the version installed: bin/magento --version
Caveat Security patches typically have minimal breaking changes; always review release notes for any configuration or template changes before deploying to production

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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