CVE-2026-21292: Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)

Published Mar 11, 2026
·
Updated

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 low-privileged attacker attacker to inject malicious scripts into vulnerable form fields. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field.

Affected Software

184 affected components
Adobe Commerce<2.4.9-alpha3
Adobe Commerce B2b<1.3.3
Adobe Commerce B2b=1.3.3
Adobe Commerce B2b=1.3.3-p1
Adobe Commerce B2b=1.3.3-p10
Adobe Commerce B2b=1.3.3-p11
Adobe Commerce B2b=1.3.3-p12
Adobe Commerce B2b=1.3.3-p13
Adobe Commerce B2b=1.3.3-p14
Adobe Commerce B2b=1.3.3-p15
Adobe Commerce B2b=1.3.3-p16
Adobe Commerce B2b=1.3.3-p2
Adobe Commerce B2b=1.3.3-p3
Adobe Commerce B2b=1.3.3-p4
Adobe Commerce B2b=1.3.3-p5
Adobe Commerce B2b=1.3.3-p6
Adobe Commerce B2b=1.3.3-p7
Adobe Commerce B2b=1.3.3-p8
Adobe Commerce B2b=1.3.3-p9
Adobe Commerce B2b=1.3.4
Adobe Commerce B2b=1.3.4-p1
Adobe Commerce B2b=1.3.4-p10
Adobe Commerce B2b=1.3.4-p11
Adobe Commerce B2b=1.3.4-p12
Adobe Commerce B2b=1.3.4-p13
Adobe Commerce B2b=1.3.4-p14
Adobe Commerce B2b=1.3.4-p15
Adobe Commerce B2b=1.3.4-p2
Adobe Commerce B2b=1.3.4-p3
Adobe Commerce B2b=1.3.4-p4
Adobe Commerce B2b=1.3.4-p5
Adobe Commerce B2b=1.3.4-p6
Adobe Commerce B2b=1.3.4-p7
Adobe Commerce B2b=1.3.4-p8
Adobe Commerce B2b=1.3.4-p9
Adobe Commerce B2b=1.3.5
Adobe Commerce B2b=1.3.5-p1
Adobe Commerce B2b=1.3.5-p10
Adobe Commerce B2b=1.3.5-p11
Adobe Commerce B2b=1.3.5-p12
Adobe Commerce B2b=1.3.5-p13
Adobe Commerce B2b=1.3.5-p2
Adobe Commerce B2b=1.3.5-p3
Adobe Commerce B2b=1.3.5-p4
Adobe Commerce B2b=1.3.5-p5
Adobe Commerce B2b=1.3.5-p6
Adobe Commerce B2b=1.3.5-p7
Adobe Commerce B2b=1.3.5-p8
Adobe Commerce B2b=1.3.5-p9
Adobe Commerce B2b=1.4.2
Adobe Commerce B2b=1.4.2-p1
Adobe Commerce B2b=1.4.2-p2
Adobe Commerce B2b=1.4.2-p3
Adobe Commerce B2b=1.4.2-p4
Adobe Commerce B2b=1.4.2-p5
Adobe Commerce B2b=1.4.2-p6
Adobe Commerce B2b=1.4.2-p7
Adobe Commerce B2b=1.4.2-p8
Adobe Commerce B2b=1.5.2
Adobe Commerce B2b=1.5.2-p1
Adobe Commerce B2b=1.5.2-p2
Adobe Commerce B2b=1.5.2-p3
Adobe Commerce B2b=1.5.3-alpha1
Adobe Commerce B2b=1.5.3-alpha2
Adobe Commerce B2b=1.5.3-alpha3
Adobe Commerce<2.4.4
Adobe Commerce=2.4.4
Adobe Commerce=2.4.4-p1
Adobe Commerce=2.4.4-p10
Adobe Commerce=2.4.4-p11
Adobe Commerce=2.4.4-p12
Adobe Commerce=2.4.4-p13
Adobe Commerce=2.4.4-p14
Adobe Commerce=2.4.4-p15
Adobe Commerce=2.4.4-p16
Adobe Commerce=2.4.4-p2
Adobe Commerce=2.4.4-p3
Adobe Commerce=2.4.4-p4
Adobe Commerce=2.4.4-p5
Adobe Commerce=2.4.4-p6
Adobe Commerce=2.4.4-p7
Adobe Commerce=2.4.4-p8
Adobe Commerce=2.4.4-p9
Adobe Commerce=2.4.5
Adobe Commerce=2.4.5-p1
Adobe Commerce=2.4.5-p10
Adobe Commerce=2.4.5-p11
Adobe Commerce=2.4.5-p12
Adobe Commerce=2.4.5-p13
Adobe Commerce=2.4.5-p14
Adobe Commerce=2.4.5-p15
Adobe Commerce=2.4.5-p2
Adobe Commerce=2.4.5-p3
Adobe Commerce=2.4.5-p4
Adobe Commerce=2.4.5-p5
Adobe Commerce=2.4.5-p6
Adobe Commerce=2.4.5-p7
Adobe Commerce=2.4.5-p8
Adobe Commerce=2.4.5-p9
Adobe Commerce=2.4.6
Adobe Commerce=2.4.6-p1
Adobe Commerce=2.4.6-p10
Adobe Commerce=2.4.6-p11
Adobe Commerce=2.4.6-p12
Adobe Commerce=2.4.6-p13
Adobe Commerce=2.4.6-p2
Adobe Commerce=2.4.6-p3
Adobe Commerce=2.4.6-p4
Adobe Commerce=2.4.6-p5
Adobe Commerce=2.4.6-p6
Adobe Commerce=2.4.6-p7
Adobe Commerce=2.4.6-p8
Adobe Commerce=2.4.6-p9
Adobe Commerce=2.4.7
Adobe Commerce=2.4.7-b1
Adobe Commerce=2.4.7-b2
Adobe Commerce=2.4.7-beta3
Adobe Commerce=2.4.7-p1
Adobe Commerce=2.4.7-p2
Adobe Commerce=2.4.7-p3
Adobe Commerce=2.4.7-p4
Adobe Commerce=2.4.7-p5
Adobe Commerce=2.4.7-p6
Adobe Commerce=2.4.7-p7
Adobe Commerce=2.4.7-p8
Adobe Commerce=2.4.8
Adobe Commerce=2.4.8-beta1
Adobe Commerce=2.4.8-beta2
Adobe Commerce=2.4.8-p1
Adobe Commerce=2.4.8-p2
Adobe Commerce=2.4.8-p3
Adobe Commerce=2.4.9-alpha1
Adobe Commerce=2.4.9-alpha2
Adobe Commerce=2.4.9-alpha3
Adobe Magento<2.4.5
Adobe Magento=2.4.5
Adobe Magento=2.4.5-p1
Adobe Magento=2.4.5-p10
Adobe Magento=2.4.5-p11
Adobe Magento=2.4.5-p12
Adobe Magento=2.4.5-p13
Adobe Magento=2.4.5-p14
Adobe Magento=2.4.5-p15
Adobe Magento=2.4.5-p2
Adobe Magento=2.4.5-p3
Adobe Magento=2.4.5-p4
Adobe Magento=2.4.5-p5
Adobe Magento=2.4.5-p6
Adobe Magento=2.4.5-p7
Adobe Magento=2.4.5-p8
Adobe Magento=2.4.5-p9
Adobe Magento=2.4.6
Adobe Magento=2.4.6-p1
Adobe Magento=2.4.6-p10
Adobe Magento=2.4.6-p11
Adobe Magento=2.4.6-p12
Adobe Magento=2.4.6-p13
Adobe Magento=2.4.6-p2
Adobe Magento=2.4.6-p3
Adobe Magento=2.4.6-p4
Adobe Magento=2.4.6-p5
Adobe Magento=2.4.6-p6
Adobe Magento=2.4.6-p7
Adobe Magento=2.4.6-p8
Adobe Magento=2.4.6-p9
Adobe Magento=2.4.7
Adobe Magento=2.4.7-b1
Adobe Magento=2.4.7-b2
Adobe Magento=2.4.7-beta3
Adobe Magento=2.4.7-p1
Adobe Magento=2.4.7-p2
Adobe Magento=2.4.7-p3
Adobe Magento=2.4.7-p4
Adobe Magento=2.4.7-p5
Adobe Magento=2.4.7-p6
Adobe Magento=2.4.7-p7
Adobe Magento=2.4.7-p8
Adobe Magento=2.4.8
Adobe Magento=2.4.8-beta1
Adobe Magento=2.4.8-beta2
Adobe Magento=2.4.8-p1
Adobe Magento=2.4.8-p2
Adobe Magento=2.4.8-p3
Adobe Magento=2.4.9-alpha3

Event History

Mar 11, 2026
CVE Published
via MITRE·02:19 AM
Data Sourced
via MITRE·02:19 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-21292?

The CVE-2026-21292 is considered a high severity vulnerability due to its potential for stored cross-site scripting (XSS) attacks.

2

How do I fix CVE-2026-21292?

To fix CVE-2026-21292, update Adobe Commerce to version 2.4.9-alpha4 or later, or apply available patches from Adobe.

3

Who is affected by CVE-2026-21292?

CVE-2026-21292 affects Adobe Commerce versions 2.4.9-alpha3, 2.4.8-p3, and several earlier versions of Adobe Commerce.

4

What types of attacks can exploit CVE-2026-21292?

CVE-2026-21292 can be exploited by attackers to perform stored cross-site scripting (XSS) attacks for data manipulation or unauthorized access.

5

What should I do if I can't immediately update for CVE-2026-21292?

If you cannot immediately update for CVE-2026-21292, consider implementing web application firewalls and limiting user permissions as a temporary mitigation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203