Skip to main content

Adobe Commerce CVE-2025-54267

MEDIUM
Incorrect Authorization (CWE-863)
2025-10-14 psirt@adobe.com
6.5
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged store account
  2. Exploit
    Send request to improperly authorized endpoint
  3. Execution
    Bypass authorization/escalate privileges
  4. Impact
    Modify restricted data or configuration

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid low-privileged authenticated account on the Adobe Commerce/Magento instance (CVSS PR:L; the description explicitly says 'a low-privileged attacker'), after which the attacker exploits an incorrect-authorization flaw (CWE-863) to escalate to elevated privileges. No special non-default feature is named in the advisory, and no user interaction is required (UI:N), so any instance exposing authenticated low-privilege access (customer, limited admin, API, or B2B company user - note the 'Commerce B2b' tag) to network-reachable endpoints is potentially affected. The key limiting factor is that this is NOT a pre-authentication flaw: the attacker must first possess some authenticated foothold, which reduces exposure for stores that tightly restrict account provisioning. Affected versions are 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; upgrading to the patched release removes the condition.

Impact

This is a genuine but moderate-priority issue rather than an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N = 6.5 Medium) describes a network-reachable, low-complexity privilege-escalation flaw that an attacker can trigger with only low privileges and no user interaction, but with impact limited to integrity (C:N/A:N) - meaning it corrupts/elevates authorization state rather than leaking data or causing outages. The intelligence signals are consistent and point to lower real-world urgency: EPSS is 0.43% (35th percentile), indicating low near-term exploitation probability; the CVE is NOT on the CISA KEV list; and no public PoC was provided - so exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision was supplied. There is no conflict between signals here (low EPSS, no KEV, no PoC, Medium CVSS all align), so this is a patch-in-normal-cycle item, not a drop-everything issue. One caveat to verify: the input tag labels this an 'Authentication Bypass,' but the CWE-863 (Incorrect Authorization) and the description ('low-privileged attacker ... gain unauthorized access to elevated privileges') describe privilege escalation / authorization bypass by an already-authenticated low-privileged user, not pre-auth authentication bypass - defenders should treat the PR:L (authenticated) requirement as the operative gating factor.

Exploit ScenarioDerived

An attacker who already holds a low-privileged account on the Adobe Commerce/Magento store (for example a limited admin, API user, or B2B company account) sends crafted requests to an improperly authorized endpoint and obtains elevated privileges they should not have. No end-user interaction is required (UI:N), and the result is a high-integrity impact such as modifying data or configuration reserved for higher-privileged roles. No public exploit code was identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Incorrect authorization handling in Adobe Commerce (Magento) 2.4.4 and later through 2.4.9-alpha2 allows an authenticated low-privileged user to bypass access controls and escalate to elevated privileges, enabling high-integrity-impact changes. The attack requires a valid low-privilege account (customer, limited admin, API, or B2B company user) and no user interaction, so stores with open account registration or broadly exposed authenticated endpoints carry the greatest exposure. No public exploit code or active exploitation has been identified; EPSS is low at 0.43% (35th percentile), and Adobe has released a vendor patch via advisory APSB25-94.

RemediationAI

Apply the vendor patch: Adobe published fixes for this issue in security bulletin APSB25-94 (https://helpx.adobe.com/security/products/magento/apsb25-94.html), which specifies the corrected release for each affected branch; upgrade every Commerce instance - including B2B-enabled stores - to the patched version for its track, as no explicit fixed version string is provided in the source data for this record. Because exploitation requires an existing low-privilege authenticated account (PR:L), the most effective compensating control is tightening the authenticated attack surface while patching is pending: disable open self-registration and guest account creation so attackers cannot cheaply obtain a foothold, and audit B2B company-user and custom admin roles to remove excessive privileges (trade-off: restricting registration can reduce storefront conversion, and narrowing roles can disrupt legitimate merchant workflows, so stage changes carefully). Restrict network access to admin, REST/GraphQL API, and B2B endpoints via allow-listing or a WAF/IPS rule set that flags privilege-escalation and role-change requests, and enforce multi-factor authentication and alerting on all administrative and company-admin accounts (trade-off: allow-listing can break integrations or partner access). Monitor Commerce audit and application logs for unexpected role changes, ACL modifications, or privileged actions performed by low-privilege sessions, and rotate credentials or disable suspect accounts if such activity is detected. Validate that all custom modules and third-party extensions enforcing their own authorization logic are reviewed, since they may replicate the same incorrect-authorization pattern fixed in core.

Affected Packages

composer magento/community-edition fix: 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3
composer magento/project-community-edition no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in composer

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-863 (Incorrect Authorization): the application performs an authorization check but does so incorrectly, so a user who legitimately holds low-level privileges can reach functionality or perform operations reserved for a higher privilege tier. Affected code lives in Adobe Commerce, the enterprise e-commerce platform built on the Magento Open Source codebase; the supplied tags (Authentication Bypass, Adobe, Magento, Commerce, Commerce B2b) indicate the flaw also affects the B2B module, where company users and hierarchical purchasing roles are common and where role-based access control is business-critical. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N confirms network reachability, low attack complexity, and a mandatory low-privilege authenticated foothold, with no confidentiality impact but high integrity impact, meaning an attacker can create, modify, or corrupt data, configuration, or records rather than read protected data. CPE data enumerates Adobe Commerce 2.4.4 including service packs p1 through p15, confirming the flaw is present across the full 2.4.4 maintenance line as well as later 2.4.5 through 2.4.8 patch releases and the 2.4.9-alpha2 pre-release. Because this is not a pre-authentication issue, the practical blast radius depends on how easily an attacker can obtain a low-privileged account and how permissive the instance's role assignments are.

Know when Commerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable web endpoint (AV:N/AC:L) exploitable by an already-authenticated low-privileged user (PR:L) with no interaction (UI:N); authorization bypass raises integrity to high while confidentiality and availability are unaffected.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
High
Adobe Commerce/Magento is a very widely deployed enterprise e-commerce platform
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Affected Products (CPE)CVE.org

cpe:2.3:a:adobe:commerce:2.4.4:-:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p1:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p10:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p11:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p12:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p13:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p14:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p15:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p2:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p3:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p4:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p5:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p6:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p7:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p8:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.4:p9:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.5:-:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.5:p1:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.5:p10:*:*:*:*:*:*
cpe:2.3:a:adobe:commerce:2.4.5:p11:*:*:*:*:*:*
+ 130 more
CVE-2026-71362 CRITICAL POC
9.1 Aug 11

Privilege escalation in Adobe Commerce and Magento Open Source (including Adobe Commerce B2B) lets a remote attacker gai

CVE-2024-34102 CRITICAL POC
9.8 Jun 13

Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Restriction of XML E

CVE-2021-27602 CRITICAL
9.9 Apr 13

SAP Commerce, versions - 1808, 1811, 1905, 2005, 2011, Backoffice application allows certain authorized users to create

CVE-2021-21477 CRITICAL
9.9 Feb 09

SAP Commerce Cloud, versions - 1808,1811,1905,2005,2011, enables certain users with required privileges to edit drools r

CVE-2024-45115 CRITICAL
9.8 Oct 10

Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Authentication v

CVE-2024-34107 CRITICAL
9.8 Jun 13

Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Access Control vulne

CVE-2022-34256 CRITICAL
9.8 Aug 16

Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improp

CVE-2021-42064 CRITICAL
9.8 Dec 14

If configured to use an Oracle database and if a query is created using the flexible search java api with a parameterize

CVE-2020-6265 CRITICAL
9.8 Jun 09

SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an

CVE-2024-20717 MEDIUM POC
5.4 Feb 15

Adobe Commerce versions 2.4.6-p3, 2.4.5-p5, 2.4.4-p6 and earlier are affected by a stored Cross-Site Scripting (XSS) vul

CVE-2026-76201 CRITICAL
9.3 Sep 08

Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B lets a remote attacker persis

CVE-2026-76200 CRITICAL
9.3 Sep 08

Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B (versions through the August

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy