Adobe Commerce (widely used e‑commerce platform); stored XSS can enable account/session compromise affecting customer transactions and storefront integrity.
CVE-2026-48413
Stored XSS in Adobe Commerce allows script injection and account/session compromise.
Is CVE-2026-48413 being exploited?
Not confirmed. CVE-2026-48413 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.63% probability of exploitation in the next 30 days.
How severe is CVE-2026-48413?
CVE-2026-48413 is rated High. 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-48413?
Not known from our data. No patch reference has been recorded for CVE-2026-48413, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-48413 affect?
CVE-2026-48413 affects Adobe Commerce (Magento) storefront/admin form fields. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48413?
Apply vendor patch when released; sanitize/escape inputs, remove malicious entries, invalidate sessions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low‑privileged attacker can store JavaScript in form fields to hijack sessions, perform actions as victims, or elevate access.
Patch when possible
- affected<= 2.4.9-2026-jul, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug
- affected<= 1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-jul
- affected<= 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul
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.