Skip to main content

Adobe Commerce CVE-2026-92922

| EUVDEUVD-2026-99214 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-13 adobe GHSA-mw54-xf6r-5925
8.1
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

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

  1. Access
    Obtain high-privileged backend account
  2. Delivery
    Inject JavaScript into vulnerable form field
  3. Exploit
    Script stored server-side
  4. Execution
    Victim admin browses affected page
  5. Persist
    Script executes in victim session
  6. Impact
    Hijack session / escalate account control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

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

Exploitation Conditions

Requires the attacker to already possess a high-privileged backend account in Adobe Commerce, Adobe Commerce B2B, or Magento Open Source with the ability to write to the affected admin form fields (PR:H). Exploitation is NOT automatic: a second victim user must subsequently browse to the page that renders the stored field for the injected JavaScript to execute (UI:R). The payload persists server-side (stored XSS), and the scope change (S:C) reflects impact on the victim's browser/session security context rather than the injecting account. Limiting factors: no unauthenticated or low-privilege path exists, so the flaw is primarily an insider-abuse or post-compromise privilege-escalation vector rather than a remotely exploitable entry point.

Impact

This is a medium-to-moderate real-world priority rather than a top-tier emergency, despite the 8.1 'High' CVSS base score. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C) shows the score is inflated primarily by the scope change (S:C) and dual High confidentiality/integrity impact, but it is gated by two significant barriers: PR:H means the attacker must already hold high (administrative) privileges in the Commerce/Magento backend, and UI:R means a victim must actively browse the page hosting the injected script. No EPSS score, KEV listing, or public POC was provided in the intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The chief signals therefore point the same direction and are not in conflict: a high-privilege-required stored XSS is realistically an insider/post-compromise or privilege-abuse issue rather than a mass-exploitable internet-facing flaw. EPSS is absent (not low) and should not be read as either confirmation or exoneration. The main caveat: the input provides no EPSS/KEV/POC data at all, so the exploitation-likelihood dimension is unmeasured rather than confirmed-benign - treat prioritization as 'patch in normal cycle' absent new exploitation signals.

Exploit ScenarioDerived

A malicious or compromised administrator (or a lower-admin with form-editing rights) injects JavaScript into a vulnerable backend form field in Adobe Commerce/Magento. When another privileged user later views the page rendering that field, the script executes in their authenticated session, allowing the attacker to hijack that session or escalate access. No public exploit code was identified in the provided intelligence; exploitation requires an existing high-privilege foothold plus victim interaction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.9% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 13, 2026

Stored cross-site scripting in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows a high-privileged backend user to persist malicious JavaScript into vulnerable admin form fields, which then executes in the browser of any other user who views the affected page, potentially hijacking that victim's account or session. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N, 8.1 High) requires the attacker to already hold a high-privileged backend account (PR:H) and requires a second victim to browse the poisoned page (UI:R); no unauthenticated or low-privilege entry path exists, so this is primarily an insider-abuse or post-compromise escalation vector. There is no public exploit code identified at time of analysis, and despite the High base score our assessment puts real-world priority at medium-to-moderate rather than emergency, with vendor fixes described in Adobe bulletin APSB26-153.

RemediationAI

Patch status is: Patch available per vendor advisory - Adobe documents the fix in security bulletin APSB26-153 (https://www.adobe.com/trust/security/products/commerce/apsb26-153.html), which lists the exact patched Commerce, Commerce B2B, and Magento Open Source versions; because the supplied reference data does not enumerate a specific fix version, apply the version named in that bulletin rather than assuming your current build is unaffected. Until patching is complete, the highest-value compensating controls are access-side: strictly limit who holds backend accounts capable of editing CMS pages/blocks, product, customer, or B2B company/quote fields, and audit existing high-privilege admins, since PR:H means the injector must already be a trusted backend user - the trade-off is reduced operational flexibility for content and merchandising teams. Configure the admin panel behind IP allow-listing or a VPN so stored payloads cannot be triggered by external victims, recognizing this frustrates legitimate remote administration. Deploy a strict Content-Security-Policy on admin and storefront responses to blunt script execution, accepting that Magento's inline frontend scripts often require nonce or hash tuning and CSP may break third-party extensions. Where feasible, add output-encoding/sanitization at the template layer for admin-rendered fields and review recent CMS, product, and company records for injected markup. Finally, treat any compromise of an admin account as a detection trigger: monitor admin audit logs for unexpected content edits and unexpected JavaScript in stored fields, on the understanding that this is an insider/post-compromise escalation path rather than a remotely exploitable initial foothold.

Affected VersionsENISA

Adobe Commerce B2B 0 ≤1.5.3-2026-sep, 1.5.2-2026-sep, 1.4.2-2026-sep, 1.3.4-2026-sep, 1.3.3-2026-sep
Adobe Commerce 0 ≤2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sep, 2.4.6-2026-sep, 2.4.5-2026-sep, 2.4.4-2026-sep
Magento Open Source 0 ≤2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sep

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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-79 (Improper Neutralization of Input During Web Page Generation), specifically the stored (persistent) variant: attacker-supplied JavaScript is written into a server-side field and later rendered without adequate output encoding or input sanitization. Adobe Commerce, Adobe Commerce B2B, and Magento Open Source are the same PHP/MySQL e-commerce codebase family, where administrative forms (CMS pages/blocks, product attributes, customer and order fields, and B2B company/quote data) are rendered back to other backend or storefront users. The CVSS vector's scope change (S:C) is meaningful here - the injected script executes in the security context of the victim's browser and session rather than that of the injecting account, which is why confidentiality and integrity are both rated High while availability is None. The PR:H/UI:R combination is what constrains this class of bug: the injector must be a trusted backend actor, and the payload only fires when a second, separate user loads the contaminated page. The CPE entries use version wildcards (cpe:2.3:a:adobe:adobe_commerce:*, adobe_commerce_b2b:*, magento_open_source:*), indicating the advisory maps the issue to the product families rather than to a single enumerated build, so the authoritative version ranges must be read from the Adobe bulletin.

Know when Adobe 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 8.1 HIGH
AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
vuln.today AI 8.1 HIGH

Injection requires administrative backend access (PR:H) over the network (AV:N); a victim must browse the stored field (UI:R), and script execution in the victim's separate session context yields S:C with high C/I and no availability impact.

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

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

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

DescriptionCVE.org

Adobe Commerce is affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field, potentially gaining elevated access or control over the victim's account or session. Scope is changed.

Executive ViewAI

Why It Matters

Organizations using Adobe Commerce, Adobe Commerce B2B, or Magento Open Source face a high-severity risk where a trusted insider with backend access could compromise other administrative users, leading to potential data breaches or operational disruption. This vulnerability requires an already compromised high-privilege account and user interaction, but the impact could be significant for e-commerce platforms handling sensitive customer and payment data. Leadership should ensure strict access controls and monitoring are in place while awaiting a vendor patch.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict backend access to trusted users, enforce multi-factor authentication, implement content security policy (CSP), monitor admin activity for anomalies, and deploy web application firewall rules to block XSS attempts.

Threat Intelligence Overview

EPSS Score
0.9%
Top 41% exploitable
Prevalence
High
Adobe Commerce/Magento is a widely deployed enterprise e-commerce platform
Data Quality
4 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC No
EPSS 0.9%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Medium

Priority Score

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2026-75650 CRITICAL POC
10.0 Sep 07

Server-side template injection in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows remote unauthentica

CVE-2026-48356 CRITICAL
9.3 Jul 14

Arbitrary code execution in Adobe Commerce, Magento Open Source, Adobe Commerce B2B, and the Adobe Commerce Webhooks Plu

CVE-2026-47992 HIGH
7.2 Jul 14

SQL injection in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks Plugin allows

CVE-2026-47996 MEDIUM
6.8 Jul 14

Security feature bypass in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks plug

CVE-2026-103849 CRITICAL
10.0 Oct 13

Unauthenticated remote code execution affects Adobe Commerce, Adobe Commerce B2B, and Magento Open Source through improp

CVE-2026-92909 CRITICAL
9.8 Oct 13

Remote, low-complexity code execution is possible in Adobe Commerce, Adobe Commerce B2B and Magento Open Source through

CVE-2021-36020 CRITICAL
9.8 Sep 01

Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an XML Inj

CVE-2026-100133 CRITICAL
9.3 Oct 13

Stored cross-site scripting in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows a remote attacker to p

CVE-2026-91013 CRITICAL
9.3 Oct 13

Stored cross-site scripting (XSS) in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows an attacker who

CVE-2026-48358 CRITICAL
9.1 Jul 14

Arbitrary code execution in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks Plu

CVE-2026-92464 CRITICAL
9.1 Oct 13

Arbitrary code execution is achievable in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source by an attacker who

CVE-2026-47994 HIGH
8.7 Jul 14

Stored cross-site scripting in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source lets a low-privileged authent

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