How severe is GHSA-mj32-r678-7mvp?

No CVSS score has been assigned to GHSA-mj32-r678-7mvp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mj32-r678-7mvp?

GHSA-mj32-r678-7mvp affects the following packages: craftcms/commerce (Packagist), craftcms/commerce (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mj32-r678-7mvp?

Update craftcms/commerce to 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj32-r678-7mvp is resolved across your whole dependency graph.

How do I detect GHSA-mj32-r678-7mvp 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-mj32-r678-7mvp 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-mj32-r678-7mvp?

O3 pinpoints whether GHSA-mj32-r678-7mvp 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-mj32-r678-7mvp actively exploited in the wild?

No public exploit code has been indexed for GHSA-mj32-r678-7mvp 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-mj32-r678-7mvp?

GHSA-mj32-r678-7mvp 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-mj32-r678-7mvp published, and has it been updated?

GHSA-mj32-r678-7mvp was published on March 10, 2026 and was last updated on March 13, 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-mj32-r678-7mvp

Fix: craftcms/commerce@b0683e0

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

Craft Commerce has stored XSS in Craft Commerce Order Details Slideout

Also known asCVE-2026-29177

Published

Mar 10, 2026

Updated

Mar 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

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

A Stored Cross-Site Scripting (XSS) vulnerability exists in the Craft Commerce Order details. Malicious JavaScript can be injected via the Shipping Method Name, Order Reference, or Site Name. When a user opens the order details slideout via a double-click on the order index page, the injected payload executes.

Reproduction Steps

Navigate to Commerce -> Store Management -> Shipping Methods.
Click "New Shipping Method".
In the Name field, enter the following XSS payload:
```
<img src=x onerror=alert('XSS_Shipping')>
```
Save the Shipping Method.
Place a new order or edit an existing order.
Set the order's Shipping Method to the one created in the previous steps.
Navigate to the Orders index page (/admin/commerce/orders).
Double-click the target order to open the details slideout.
Result: The XSS payload executes.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/commerce`	≥ 4.0.0&&< 4.10.2	4.10.2
🐘Packagist	`craftcms/commerce`	≥ 5.0.0&&< 5.5.3	5.5.3

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 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj32-r678-7mvp 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-mj32-r678-7mvp 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-mj32-r678-7mvp. 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 Cross-Site Scripting (XSS) vulnerability exists in the Craft Commerce Order details. Malicious JavaScript can be injected via the **Shipping Method Name**, **Order Reference**, or **Site Name**. When a user opens the order details slideout via a double-click on the order index page, the injected payload executes. ## Reproduction Steps 1. Navigate to **Commerce** -> **Store Management** -> **Shipping Methods**. 1. Click "New Shipping Method". 1. In the **Name** field, enter the following XSS payload: ```html <img src=x onerror=alert('XSS_Shipping')> ``` 1. Save

O3 Security · Impact-Aware SCA

Is GHSA-mj32-r678-7mvp in your dependencies?

O3 detects GHSA-mj32-r678-7mvp 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