Skip to main content
VulnerabilityPublished Updated

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

Affects Adobe CommerceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% 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:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 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 29 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

Until an official fix is released, restrict high-privileged user access to trusted personnel only and monitor for suspicious activity involving form inputs. Avoid exposing vulnerable form fields to untrusted users. Follow Adobe's updates closely for any released patches or mitigation instructions.

Description

Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 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. Scope is changed.

References

Community reviews

Loading reviews…