External risk intelligence

Adobe Commerce Stored Cross-Site Scripting Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-100133

Adobe Commerce is a web-based e-commerce platform designed to be publicly accessible as a storefront or administrative portal. Because it is a web application meant for external users and administrators, the vulnerable form fields are commonly exposed to the public internet in standard deployment patterns.

Cross-site Scripting

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce. The issue allows attackers to inject malicious scripts into form fields, which could then be executed in a user's browser. This could potentially lead to unauthorized access or control of a victim's account or session.

  • Attackers can insert harmful code into forms.
  • High impact if users visit affected pages.
  • Confirm if Adobe Commerce is in use.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by targeting public-facing form fields within Adobe Commerce. Users who interact with these compromised fields, or view pages containing them, may inadvertently trigger the injection of malicious scripts. This could lead to unauthorized execution of JavaScript in their browser, potentially resulting in elevated access or control over their account or session.

  • No authentication required for attacker.
  • Malicious script injected via form fields.
  • Risk of account takeover or session hijacking.

Live Threat

Current exploitation, exposure, and threat context

A stored cross-site scripting vulnerability in Adobe Commerce could allow an attacker to inject malicious scripts into form fields. When a victim visits a page with a vulnerable field, these scripts may execute in their browser, potentially leading to unauthorized access or control of their account or session.

  • Compromised user accounts and sessions.
  • Malicious scripts executed via vulnerable fields.
  • Unauthorized account access or control.

Operational Fix

Recommended remediation, mitigation, and detection steps

Adobe Commerce's stored XSS vulnerability impacts product owners and the infrastructure teams supporting the e-commerce platform. The first practical step is to inventory all Adobe Commerce instances, assess their internet exposure, and identify the business owner for each. Subsequently, remediation plans should be developed based on the assessed risk and criticality, prioritizing instances that are externally accessible and actively used.

  • Product owners must own the remediation effort.
  • Verify external accessibility and business criticality.
  • Plan for vendor coordination and patching.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Adobe Commerce?

Adobe Commerce is a comprehensive web-based e-commerce platform. Businesses use it to build and manage online storefronts and administrative portals. Because it handles product catalogs, customer data, and checkout processes, it is typically designed to remain publicly accessible to support shopping and management tasks.

What is the vulnerability behind CVE-2026-100133?

This vulnerability is classified as Stored Cross-Site Scripting (CWE-79). In plain terms, it means the application fails to properly sanitize input in certain form fields. An attacker can save malicious JavaScript code into these fields, which then executes automatically in the browser of any user who views the page where that data is displayed.

How does an attacker trigger this XSS flaw?

An attacker triggers this by submitting malicious scripts into specific, vulnerable form fields within the application. This does not require the attacker to have an account or elevated privileges. Simply interacting with publicly available forms is sufficient. Merely viewing the site or browsing existing content does not trigger the bug; the script must be intentionally injected into a field first.

Do I need to worry if my Adobe Commerce site is online?

Yes. According to Halo Surface Signal, Adobe Commerce is designed for public access, making these vulnerable form fields naturally reachable from the internet. If your instance is internet-facing, it is accessible to anyone, increasing the risk that an unauthorized party could inject code that compromises the sessions of your customers or administrators.

How should I begin responding to this threat?

Start by performing a complete inventory of all Adobe Commerce instances in your environment. Once identified, determine which instances are exposed to the internet and confirm who manages them. Use this information to coordinate with the appropriate teams to assess the criticality of each site and prepare for vendor-supplied updates or security mitigations.

References