Adobe Commerce (Magento) is a widely used e-commerce platform; stored XSS enabling session/account takeover can disrupt online sales, customer accounts, and trust across many organizations.
CVE-2026-47994
Stored XSS in Adobe Commerce allows persistent script injection and potential account/session takeover.
Is CVE-2026-47994 being exploited?
Not confirmed. CVE-2026-47994 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-47994?
CVE-2026-47994 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47994?
Yes. A fix has been recorded for CVE-2026-47994. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47994 affect?
CVE-2026-47994 affects Adobe Commerce (Magento) storefronts, Adobe Commerce admin interfaces. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47994?
Apply vendor patch when available, sanitize inputs, enable WAF/filters
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS via form fields lets a low-privileged attacker inject JS to hijack sessions, perform account takeover, escalate privileges, or execute actions as victims.
Patch when possible
- affected<= 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18
- affected<= 1.5.3, 1.5.2-p5, 1.4.2-p10, 1.3.4-p17, 1.3.3-p18
- affected<= 1.20.0
- affected<= 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.