Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-29173: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in craftcms commerce

0
Low
VulnerabilityCVE-2026-29173cvecve-2026-29173cwe-79
Published: Tue Mar 10 2026 (03/10/2026, 19:54:25 UTC)
Source: CVE Database V5
Vendor/Project: craftcms
Product: commerce

Description

Craft Commerce is an ecommerce platform for Craft CMS. Prior to 4.10.2 and 5.5.3, a stored XSS vulnerability exists when a user tries to update the Order Status from the Commerce Orders Table. The Order Status Name is rendered without proper escaping, allowing script execution to occur. This vulnerability is fixed in 4.10.2 and 5.5.3.

AI-Powered Analysis

AILast updated: 03/10/2026, 20:30:38 UTC

Technical Analysis

CVE-2026-29173 is a stored cross-site scripting (XSS) vulnerability classified under CWE-79 affecting Craft Commerce, a widely used ecommerce plugin for Craft CMS. The vulnerability arises because the Order Status Name field is not properly escaped when rendered in the Commerce Orders Table interface. An authenticated user with permission to update order statuses can inject malicious JavaScript code into the Order Status Name. When other users, such as administrators or staff, view the orders table, the injected script executes in their browsers, potentially leading to session hijacking, credential theft, or unauthorized actions within the CMS environment. The vulnerability affects Craft Commerce versions from 4.0.0 up to but not including 4.10.2, and from 5.0.0 up to but not including 5.5.3. The flaw requires the attacker to have authenticated access with privileges to modify order statuses, and user interaction is necessary for the malicious script to execute (i.e., viewing the affected page). The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required for the attack vector but privileges are required for the vulnerability (PR:H), user interaction required, and low scope impact. No known active exploits have been reported. The vendor has addressed the issue in versions 4.10.2 and 5.5.3 by properly escaping the Order Status Name during rendering, mitigating the risk of script injection.

Potential Impact

The primary impact of this vulnerability is the potential for stored XSS attacks within the Craft Commerce administrative interface. Successful exploitation could allow attackers to execute arbitrary JavaScript in the context of other authenticated users, potentially leading to session hijacking, theft of sensitive information, or performing unauthorized actions on behalf of legitimate users. However, the requirement for authenticated access with privileges to update order statuses limits the attack surface to trusted users or compromised accounts. The vulnerability does not affect the confidentiality, integrity, or availability of the underlying server directly but can compromise user sessions and data confidentiality within the CMS environment. Organizations using affected versions of Craft Commerce may face risks of internal account compromise or lateral movement if attackers leverage this vulnerability in combination with other weaknesses. Since no public exploits are known, the immediate risk is low, but the vulnerability should be addressed promptly to prevent potential abuse, especially in environments with multiple administrators or staff members accessing the orders interface.

Mitigation Recommendations

Organizations should upgrade Craft Commerce to versions 4.10.2 or 5.5.3 or later, where this vulnerability is fixed. Until upgrades can be performed, administrators should restrict permissions to update order statuses to only highly trusted users to reduce the risk of malicious input. Implementing strict input validation and output encoding on all user-supplied data fields within the CMS can further mitigate XSS risks. Additionally, enabling Content Security Policy (CSP) headers can help limit the impact of any injected scripts by restricting script execution sources. Regularly auditing user roles and permissions to minimize privilege exposure and monitoring logs for suspicious activity related to order status updates are recommended. Educating users about the risks of XSS and encouraging cautious behavior when interacting with order management interfaces can also reduce exploitation likelihood. Finally, applying web application firewalls (WAFs) with rules targeting XSS payloads may provide an additional layer of defense.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-04T14:44:00.712Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69b07bba2f860ef943b24cc5

Added to database: 3/10/2026, 8:14:50 PM

Last enriched: 3/10/2026, 8:30:38 PM

Last updated: 3/13/2026, 3:21:52 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses