GHSA-2H2M-V2MG-656C
Vulnerability from github – Published: 2026-02-02 22:44 – Updated: 2026-02-03 21:40
VLAI?
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
- Log in as attacker with admin permissions.
- Go to Commerce -> Settings -> Product Types (
/admin/commerce/settings/producttypes). - Create a new Product Type.
- Set Name to:
<img src=x onerror="alert('XSS-ProductType')" hidden>
- Save the Product Type.
- Go to Users -> Edit any user -> Click on Permissions tab (
/admin/users/{UserID}/permissions). - Alert fires instantly (when the Product Type checkbox renders).
Resources
https://github.com/craftcms/commerce/commit/7e1dedf06038c8e70dce0187b7048d4ab8ffb75c
Severity ?
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 5.5.1"
},
"package": {
"ecosystem": "Packagist",
"name": "craftcms/commerce"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.5.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 4.10.0"
},
"package": {
"ecosystem": "Packagist",
"name": "craftcms/commerce"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-RC1"
},
{
"fixed": "4.10.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25484"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-02T22:44:05Z",
"nvd_published_at": "2026-02-03T19:16:25Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nStored XSS via Product Type names. The name is not sanitized when displayed in user permissions settings.\n\nThe 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.\n\nUsers are recommended to update to the patched 5.5.2 release to mitigate the issue.\n\n---\n## Proof of Concept\n\n### Required Permissions (Attacker)\n\n- Admin access (to edit Commerce settings)\n\n### Steps to Reproduce\n\n1. Log in as attacker with admin permissions.\n2. Go to **Commerce** -\u003e **Settings** -\u003e **Product Types** (`/admin/commerce/settings/producttypes`).\n3. Create a new Product Type.\n4. Set **Name** to:\n```html\n\u003cimg src=x onerror=\"alert(\u0027XSS-ProductType\u0027)\" hidden\u003e\n```\n5. Save the Product Type.\n6. Go to **Users** -\u003e Edit any user -\u003e Click on **Permissions** tab (`/admin/users/{UserID}/permissions`).\n7. Alert fires instantly (when the Product Type checkbox renders).\n\n## Resources\n\nhttps://github.com/craftcms/commerce/commit/7e1dedf06038c8e70dce0187b7048d4ab8ffb75c",
"id": "GHSA-2h2m-v2mg-656c",
"modified": "2026-02-03T21:40:06Z",
"published": "2026-02-02T22:44:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/craftcms/commerce/security/advisories/GHSA-2h2m-v2mg-656c"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25484"
},
{
"type": "WEB",
"url": "https://github.com/craftcms/commerce/commit/7e1dedf06038c8e70dce0187b7048d4ab8ffb75c"
},
{
"type": "PACKAGE",
"url": "https://github.com/craftcms/commerce"
},
{
"type": "WEB",
"url": "https://github.com/craftcms/commerce/releases/tag/4.10.1"
},
{
"type": "WEB",
"url": "https://github.com/craftcms/commerce/releases/tag/5.5.2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Craft Commerce has Stored XSS in Product Type Name"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…