Advisory

GHSA-2h2m-v2mg-656c

Also known as: CVE-2026-25484

Summary

Craft Commerce has Stored XSS in Product Type Name

Details

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).

Resources

https://github.com/craftcms/commerce/commit/7e1dedf06038c8e70dce0187b7048d4ab8ffb75c

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-02-02 22:44 UTC
Modified
2026-02-03 21:47 UTC

Affected packages and fixes

craftcms/commerce

Packagist · All systems

Affected

  • introduced 5.0.0, fixed 5.5.2 (ecosystem)

Fixed versions

5.5.2

Fix

The export has no generic command for this ecosystem.

craftcms/commerce

Packagist · All systems

Affected

  • introduced 4.0.0-RC1, fixed 4.10.1 (ecosystem)

Fixed versions

4.10.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences