How severe is GHSA-2h2m-v2mg-656c?

No CVSS score has been assigned to GHSA-2h2m-v2mg-656c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2h2m-v2mg-656c?

GHSA-2h2m-v2mg-656c affects the following packages: craftcms/commerce (Packagist), craftcms/commerce (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2h2m-v2mg-656c?

Update craftcms/commerce to 5.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h2m-v2mg-656c is resolved across your whole dependency graph.

How do I detect GHSA-2h2m-v2mg-656c in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/commerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2h2m-v2mg-656c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2h2m-v2mg-656c?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2h2m-v2mg-656c can be triaged on real exposure rather than presence alone.

Is GHSA-2h2m-v2mg-656c actively exploited in the wild?

No public exploit code has been indexed for GHSA-2h2m-v2mg-656c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2h2m-v2mg-656c?

GHSA-2h2m-v2mg-656c has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2h2m-v2mg-656c?

GHSA-2h2m-v2mg-656c is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2h2m-v2mg-656c published, and has it been updated?

GHSA-2h2m-v2mg-656c was published on February 2, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-2h2m-v2mg-656c — craftcms/commerce

Fix: craftcms/commerce@7e1dedf

GHSA-2h2m-v2mg-656c is a Cross-site Scripting (XSS) vulnerability in craftcms/commerce. A fix is available for craftcms/commerce — see the affected versions and patch details below.

Craft Commerce has Stored XSS in Product Type Name

Also known asCVE-2026-25484

Published

Feb 2, 2026

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2h2m-v2mg-656c.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘craftcms/commerce🐘craftcms/commerce

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/commerce`	≥ 5.0.0&&< 5.5.2	5.5.2`composer require craftcms/commerce:^5.5.2`
🐘Packagist	`craftcms/commerce`	≥ 4.0.0-RC1&&< 4.10.1	4.10.1`composer require craftcms/commerce:^4.10.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/commerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/commerce to 5.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h2m-v2mg-656c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2h2m-v2mg-656c can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2h2m-v2mg-656c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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** -

O3 Security · Impact-Aware SCA

Is GHSA-2h2m-v2mg-656c in your dependencies?

O3 Security finds GHSA-2h2m-v2mg-656c across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works