What is CVE-2026-29177?

CVE-2026-29177 is a low-severity cross-site scripting (XSS) vulnerability in craftcms/commerce (composer), affecting versions >= 4.0.0, <= 4.10.1. It is fixed in 4.10.2, 5.5.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of craftcms/commerce are affected by CVE-2026-29177?

craftcms/commerce (composer) versions >= 4.0.0, <= 4.10.1 is affected.

Is there a fix for CVE-2026-29177?

Yes. CVE-2026-29177 is fixed in 4.10.2, 5.5.3. Upgrade to this version or later.

Is CVE-2026-29177 exploitable, and should I be worried?

Whether CVE-2026-29177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-29177 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-29177 in craftcms/commerce

Q: Which versions of craftcms/commerce are affected by CVE-2026-29177?

craftcms/commerce (composer) versions >= 4.0.0, <= 4.10.1 is affected.

Q: Is there a fix for CVE-2026-29177?

Yes. CVE-2026-29177 is fixed in 4.10.2, 5.5.3. Upgrade to this version or later.

Q: Is CVE-2026-29177 exploitable, and should I be worried?

Whether CVE-2026-29177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-29177 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-29177?

Upgrade: craftcms/commerce to 4.10.2 or later, craftcms/commerce to 5.5.3 or later.

Summary

Craft Commerce has stored XSS in Craft Commerce Order Details Slideout

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.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

craftcms/commerce (>= 4.0.0, <= 4.10.1) craftcms/commerce (>= 5.0.0, <= 5.5.2)

Security releases

craftcms/commerce → 4.10.2 (composer) craftcms/commerce → 5.5.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

craftcms/commerce to 4.10.2 or later; craftcms/commerce to 5.5.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-29177? CVE-2026-29177 is a low-severity cross-site scripting (XSS) vulnerability in craftcms/commerce (composer), affecting versions >= 4.0.0, <= 4.10.1. It is fixed in 4.10.2, 5.5.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of craftcms/commerce are affected by CVE-2026-29177? craftcms/commerce (composer) versions >= 4.0.0, <= 4.10.1 is affected.
Is there a fix for CVE-2026-29177? Yes. CVE-2026-29177 is fixed in 4.10.2, 5.5.3. Upgrade to this version or later.
Is CVE-2026-29177 exploitable, and should I be worried? Whether CVE-2026-29177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-29177 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-29177?
- Upgrade craftcms/commerce to 4.10.2 or later
- Upgrade craftcms/commerce to 5.5.3 or later

Other vulnerabilities in craftcms/commerce

CVE-IDSeverityPackage summary

CVE-2026-55795Mediumcraftcms/commerce: Craft Commerce: Coupon Code Brute-Force via Rate Limit Bypass GHSA-78VR-Q6CF-C7P6Mediumcraftcms/commerce: Craft Commerce: Partial Payment Amount Without Lower Bound Validation CVE-2026-32270Lowcraftcms/commerce: Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments CVE-2026-32271Highcraftcms/commerce: Craft Commerce has a SQL Injection can lead to Remote Code Execution via TotalRevenue Widget CVE-2026-32272Highcraftcms/commerce: Craft Commerce hasVariant/hasProduct Blind SQL Injection