Skip to main content
VulnerabilityPublished Updated

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

Affects Adobe CommerceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.0 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/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

Organizations should immediately upgrade Adobe Commerce to the latest patched versions once available. In the absence of patches, implement strict input validation and output encoding on all user-supplied data in form fields to prevent script injection. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Limit the number of users with high privileges capable of injecting content and enforce the principle of least privilege. Monitor logs for suspicious input patterns or unusual user activity indicative of attempted exploitation. Educate users about the risks of clicking unknown links and visiting untrusted pages to reduce the likelihood of successful user interaction-based attacks. Consider deploying Web Application Firewalls (WAFs) with rules targeting XSS payloads specific to Adobe Commerce. Regularly audit and test the application for XSS vulnerabilities using automated scanners and manual penetration testing. Maintain an incident response plan to quickly address any detected exploitation attempts.

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) 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. 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…