Skip to main content
VulnerabilityPublished Updated

CVE-2026-21361: Adobe Commerce · Cross-site Scripting

Affects Adobe CommerceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AdobeAdobe CommerceAffected
  • =0
Fixed in–
AdobeAdobe Commerce B2BAffected
  • =0
Fixed in–
AdobeMagento Open SourceAffected
  • =0
Fixed in–

AI-suggested

  1. Apply official patches from Adobe as soon as they become available to address the vulnerability directly.
  2. Implement strict input validation and output encoding on all form fields to prevent injection of malicious scripts.
  3. Restrict administrative privileges to the minimum necessary and monitor for unusual activities to reduce the risk of high-privileged account compromise.
  4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers.
  5. Conduct regular security audits and penetration testing focused on XSS vulnerabilities within the Adobe Commerce environment.
  6. Educate users and administrators about phishing and social engineering tactics to reduce the likelihood of victims visiting malicious pages.
  7. Use web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting Adobe Commerce.
  8. Monitor logs for suspicious input patterns or repeated access to vulnerable pages to detect exploitation attempts early.

Description

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 a stored Cross-Site Scripting (XSS) vvulnerability 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. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field.

References

Community reviews

Loading reviews…