CVE-2025-47110: Adobe Commerce · Cross-site Scripting (Stored XSS)
Affects Adobe CommerceSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Commerce | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include restricting administrative access to trusted personnel and enforcing strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of privilege abuse. 2. Implement strict input validation and output encoding on all form fields, especially those accessible to high-privileged users, to prevent injection of malicious scripts. 3. Monitor and audit administrative activities and form submissions for unusual or unauthorized changes that could indicate exploitation attempts. 4. Deploy Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 5. Regularly update Adobe Commerce installations to the latest patched versions as soon as Adobe releases fixes for this vulnerability. 6. Conduct security awareness training for administrators to recognize phishing or social engineering attempts that could lead to account compromise. 7. Use web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting Adobe Commerce. 8. Review and harden user roles and permissions to ensure the principle of least privilege is enforced, minimizing the number of users with high-level access.
Description
Adobe Commerce versions 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 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 to that of other high-privileged accounts, leading to a high impact on confidentiality, integrity, and availability.