How severe is GHSA-wq2m-r96q-crrf?

No CVSS score has been assigned to GHSA-wq2m-r96q-crrf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wq2m-r96q-crrf?

GHSA-wq2m-r96q-crrf affects the following packages: craftcms/commerce (Packagist), craftcms/commerce (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wq2m-r96q-crrf?

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

How do I detect GHSA-wq2m-r96q-crrf in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/commerce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wq2m-r96q-crrf 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-wq2m-r96q-crrf?

O3 pinpoints whether GHSA-wq2m-r96q-crrf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wq2m-r96q-crrf actively exploited in the wild?

No public exploit code has been indexed for GHSA-wq2m-r96q-crrf 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 type of vulnerability is GHSA-wq2m-r96q-crrf?

GHSA-wq2m-r96q-crrf 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-wq2m-r96q-crrf published, and has it been updated?

GHSA-wq2m-r96q-crrf was published on February 2, 2026 and was last updated on February 22, 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

GHSA-wq2m-r96q-crrf

GHSA-wq2m-r96q-crrf is a Cross-site Scripting (XSS) vulnerability in craftcms/commerce. O3 Security confirms whether GHSA-wq2m-r96q-crrf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Craft Commerce has Stored XSS in Inventory Location Address Leading to Potential Privilege Escalation

Also known asCVE-2026-25490

Published

Feb 2, 2026

Updated

Feb 22, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

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

A stored XSS vulnerability in Craft Commerce allows attackers to execute malicious JavaScript in an administrator’s browser. This occurs because the 'Address Line 1' field in Inventory Locations is not properly sanitized before being displayed in the admin panel.

Proof of Concept

Required Permissions

General permissions:
- Access the control panel
- Access Craft Commerce
Craft Commerce permissions:
- Manage inventory locations
An active administrator elevated session

Steps to Reproduce

Log in to the Admin Panel with the attacker account with the permissions mentioned above.
Navigate to Commerce -> Inventory Locations -> Default (/admin/commerce/inventory-locations/1).
In the Address Line 1 field, enter the following payload:

<img src=x onerror="alert(document.domain)">

Click Save and you'll be redirected back to the Inventory Locations page.
Notice the alert proving JavaScript execution. <img width="1814" height="606" alt="alert-poc" src="https://github.com/user-attachments/assets/f08aed21-a676-4dee-85a8-d195bab85685" />

Privilege Escalation to Administrator:

Do the same steps above, but replace the payload with a malicious one.
The following payload elevates the attacker’s account to Admin if there’s already an elevated session, replace the <UserID> with the attacker id:

<img src=x onerror="fetch('/admin/users/<UserID>/permissions',{method:'POST',body:`CRAFT_CSRF_TOKEN=${Craft.csrfTokenValue}&userId=<UserID>&admin=1&action=users/save-permissions`,headers:{'content-type':'application/x-www-form-urlencoded'}})">

In another browser, log in as an admin & go to the vulnerable page (Inventory Location page).
Go back to the attacker account & notice it now has admin status.

The privilege escalation requires an elevated session. In a real-world scenario, an attacker can automate the process by forcing a logout if the victim’s session is stale; upon re-authentication, the stored XSS payload executes within a fresh elevated session to complete the attack.

Or even easier (and smarter), an attacker (using the XSS) can create a fake 'Session Expired' login modal overlay. Since it’s on the trusted domain, administrators will likely enter their credentials, sending them directly to the attacker.

Resources:

https://github.com/craftcms/commerce/commit/fa273330807807d05b564d37c88654cd772839ee

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/commerce`	≥ 5.0.0-RC1&&< 5.5.2	5.5.2
🐘Packagist	`craftcms/commerce`	≥ 4.0.0-RC1&&< 4.10.1	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-wq2m-r96q-crrf 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 pinpoints whether GHSA-wq2m-r96q-crrf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wq2m-r96q-crrf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary A stored XSS vulnerability in Craft Commerce allows attackers to execute malicious JavaScript in an administrator’s browser. This occurs because the 'Address Line 1' field in Inventory Locations is not properly sanitized before being displayed in the admin panel. ## Proof of Concept ### Required Permissions - General permissions: - Access the control panel - Access Craft Commerce - Craft Commerce permissions: - Manage inventory locations - An active administrator elevated session <img width="887" height="832" alt="req-perms" src="https://github.com/user-attachments/assets/7a9a

O3 Security · Impact-Aware SCA

Is GHSA-wq2m-r96q-crrf in your dependencies?

O3 detects GHSA-wq2m-r96q-crrf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works