Adobe Commerce versions 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 and earlier are affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized access to a feature. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
A low-privileged account can bypass an authorization control in affected Adobe Commerce releases and gain limited access to a feature. The issue is remotely reachable and needs no victim interaction, but the cited CVSS assessment indicates limited confidentiality impact without integrity or availability impact.
Executive priority
Schedule remediation through normal vulnerability-management timelines, accelerating for internet-facing stores or environments with weak account controls. The moderate score and limited stated impact reduce emergency urgency, but easy remote conditions and no interaction make prolonged exposure undesirable.
Technical view
CVE-2026-21297 is a CWE-863 incorrect-authorization flaw rated CVSS 3.1 4.3. Its vector indicates network access, low attack complexity, required low privileges, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is most likely where an affected Adobe Commerce deployment is network-accessible and an attacker can obtain low-level credentials. The bundle also lists Adobe Commerce B2B and Magento Open Source version boundaries; confirm applicability against APSB26-05 and the installed product inventory.
Exploitation context
The supplied sources support remote exploitation by a low-privileged attacker without user interaction. They do not establish anonymous exploitation, public exploit availability, or observed attacks. The CVE is not identified as CISA KEV in the supplied bundle.
Researcher notes
The affected-version data requires careful branch interpretation: the description names Adobe Commerce cutoffs, while the structured bundle also identifies Commerce B2B and Magento Open Source. Treat APSB26-05 as authoritative for product-specific version mapping. No root cause, endpoint, feature, indicators, or exploit evidence is supplied.
Mitigation direction
Review Adobe advisory APSB26-05 for the applicable product branch and fixed release.
Upgrade deployments beyond the affected release cutoff using Adobe's supported update path.
Restrict low-privileged account creation and disable unnecessary accounts until remediation is complete.
Limit administrative and sensitive feature access through existing network and identity controls.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source versions across all environments.
Compare each installed release with APSB26-05's affected and corrected version guidance.
Review low-privileged accounts for unexpected access to normally restricted features.
Examine authentication and authorization logs for anomalous feature access by low-privileged users.
After updating, verify authorization boundaries using approved non-destructive role tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.