Skip to content

Stored XSS in Product Type Name

Low
angrybrad published GHSA-2h2m-v2mg-656c Feb 2, 2026

Package

composer craftcms/commerce (Composer)

Affected versions

>= 5.0.0 <= 5.5.1
>= 4.0.0-RC1, <= 4.10.0

Patched versions

5.5.2
4.10.1

Description

Summary

Stored XSS via Product Type names. The name is not sanitized when displayed in user permissions settings.

The vulnerable input (source) is in Commerce (Product Type settings), but the sink is in CMS user permissions settings. Reporting to Commerce GHSA since the input originates here.

Users are recommended to update to the patched 5.5.2 release to mitigate the issue.


Proof of Concept

Required Permissions (Attacker)

  • Admin access (to edit Commerce settings)

Steps to Reproduce

  1. Log in as attacker with admin permissions.
  2. Go to Commerce -> Settings -> Product Types (/admin/commerce/settings/producttypes).
  3. Create a new Product Type.
  4. Set Name to:
<img src=x onerror="alert('XSS-ProductType')" hidden>
  1. Save the Product Type.
  2. Go to Users -> Edit any user -> Click on Permissions tab (/admin/users/{UserID}/permissions).
  3. Alert fires instantly (when the Product Type checkbox renders).

References

7e1dedf

Severity

Low

CVE ID

CVE-2026-25484

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

Credits