Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privilege user
-
ExploitIdentify improperly authorized endpoint
-
ExecutionSend request bypassing role check
-
ImpactAccess restricted resources / escalate privileges
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 | Exploitation requires the attacker to already possess a high-privilege authenticated account on the Adobe Commerce, Magento Open Source, or Adobe Commerce B2B instance (PR:H) - for example an admin, merchant, or B2B company user with an elevated role. The flaw is an incorrect authorization check (CWE-863) that fails to properly restrict access, allowing that account to reach resources or actions outside its assigned role. No user interaction is needed (UI:N) and the endpoint is network-reachable (AV:N). Limiting factors: the requirement for pre-existing high privileges eliminates unauthenticated and low-privilege attackers, and affected deployments are those running unpatched builds up to the 2026-jul releases (Commerce ≤2.4.9-2026-jul, B2B ≤1.5.3-2026-jul, Magento Open Source ≤2.4.9-2026-jul). |
| Impact | This is a moderate-severity, low-urgency issue best treated as routine patch-cycle work rather than an emergency. The signals are internally consistent and point the same direction: CVSS 3.1 base is 7.2 (High) driven mainly by C:H/I:H/A:H impact, but the exploit prerequisite is PR:H - the attacker must already hold high privileges within the Adobe Commerce admin/merchant context, which sharply narrows the realistic threat population. EPSS is 0.32% (24th percentile), consistent with the CISA SSVC decision framework which reports Exploitation: none, Automatable: no, Technical Impact: partial - three independent low-urgency signals reinforcing each other. There is no CISA KEV listing and no public exploit identified at time of analysis, so this is a real-but-low-priority issue rather than an actively exploited threat. One tension worth flagging: the CVSS vector is AV:N (network) and the tag set includes 'Authentication Bypass', which could suggest pre-auth reach, yet the description and CWE-863 (Incorrect Authorization) describe a privilege-escalation-from-existing-high-privilege scenario - the AV:N reflects that the API/web surface is reachable over the network, not that the attacker is unauthenticated. SSVC 'Technical Impact: partial' also mildly contrasts with the vector's triple-High impact, suggesting Adobe/CISA view the escalation as bounded to specific restricted resources rather than full system takeover. |
| Exploit ScenarioDerived | An attacker who already holds a high-privilege account on an Adobe Commerce / Magento store (e.g. a limited-scope admin or B2B company account) sends crafted requests to an endpoint whose authorization check is incorrectly enforced, gaining access to restricted resources or actions beyond their assigned role. No user interaction is required. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 25, 2026
Privilege escalation in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B allows an authenticated attacker who already holds a high-privilege account to bypass authorization checks and access restricted resources or perform actions outside their assigned role. The flaw is network-reachable and requires no user interaction, but it cannot be exploited by unauthenticated or low-privilege users; exploitation requires pre-existing elevated access such as an admin, merchant, or B2B company user role. No public exploit identified at time of analysis, and EPSS is 0.32% (24th percentile), with SSVC indicating exploitation none, automatable no, and partial technical impact; this aligns with a moderate-severity, low-urgency issue best handled through routine patch-cycle work.
Earlier versions of this analysis (1)
Privilege escalation in Adobe Commerce and Magento Open Source exposes restricted resources to authenticated high-privilege users through a flawed authorization check (CWE-863). Affected products span the full 2.4.x series of Adobe Commerce and Magento Open Source, plus the 1.3.x-1.5.x Adobe Commerce B2B extension. No public exploits are known, CISA SSVC rates exploitation as none, and vendor-released August 2026 patches are available across all affected release lines per advisory APSB26-92.
RemediationAI
Vendor-released patch: Adobe Commerce 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug; Adobe Commerce B2B 1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, 1.3.3-2026-aug; and Magento Open Source 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug. Apply the appropriate fix level from the Adobe advisory https://helpx.adobe.com/security/products/magento/apsb26-92.html. If immediate patching is not possible, restrict and audit high-privilege admin, merchant, and B2B company accounts, review custom modules and extensions for weak authorization checks, and enforce least-privilege role assignments; these controls may disrupt legitimate administrative workflows and require ongoing access reviews. Additional temporary controls such as limiting admin panel access by IP or deploying WAF rules for privileged endpoints can reduce exposure, but they may cause false positives and do not replace the vendor patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The underlying issue is CWE-863, Incorrect Authorization, in Adobe Commerce and related Magento Open Source / Adobe Commerce B2B code. Adobe Commerce is an e-commerce platform derived from Magento, with authorization enforced through role-based access controls for administrators, merchants, and B2B company users. CPE evidence specifically identifies Adobe Commerce 2.4.4 patch levels p1 through p18 as affected, while EUVD also scopes affected builds up to the 2026-jul releases for Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The root cause is an authorization check that fails to properly restrict a high-privilege account from reaching resources or actions outside its assigned permissions. The assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H confirms network reachability and no user interaction, but requires an authenticated high-privilege account; the impact is high across confidentiality, integrity, and availability within the context of that already privileged session.
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
Sources disagree (Low–High)AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Network-reachable endpoint with low complexity, but requires a pre-existing high-privilege account (PR:H); privilege escalation to restricted resources supports high C/I/A within the same scope.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker with high privileges could exploit this vulnerability to gain elevated access to restricted resources. Exploitation of this issue does not require user interaction.
Executive ViewAI
A high-severity authorization flaw in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B could allow an attacker who already holds an elevated role-such as an admin, merchant, or B2B company user-to bypass access controls and reach restricted resources or perform actions beyond their assigned permissions. No public exploit identified at time of analysis, but no vendor patch is currently available, so risk must be managed through interim controls. Leadership should care because a compromised or malicious high-privilege account could weaken role-based access protections and expose sensitive commerce operations or customer data.
No vendor-released patch identified at time of analysis. Interim mitigations include enforcing least privilege and just-in-time access for admin, merchant, and B2B company user roles; monitoring and alerting on privilege escalation, role changes, and access to restricted resources; restricting network access to administrative panels; and applying virtual patching or WAF rules if available while tracking Adobe's advisory for a vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Privilege escalation in Adobe Commerce and Magento Open Source (including Adobe Commerce B2B) lets a remote attacker gai
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
SAP Commerce, versions - 1808, 1811, 1905, 2005, 2011, Backoffice application allows certain authorized users to create
SAP Commerce Cloud, versions - 1808,1811,1905,2005,2011, enables certain users with required privileges to edit drools r
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
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
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
If configured to use an Oracle database and if a query is created using the flexible search java api with a parameterize
SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an
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
Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B lets a remote attacker persis
Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B (versions through the August
EUVD-2026-56846
GHSA-h84j-xhmm-hgp4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB