<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-18T05:39:36.091237+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-275353</id>
    <title>EUVD-2026-275353</title>
    <updated>2026-10-18T05:39:36.093543+00:00</updated>
    <content>EUVD-2026-275353</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-275353"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-29173</id>
    <title>fkie_cve-2026-29173</title>
    <updated>2026-10-18T05:39:36.093574+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-29173"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mqxf-2998-c6cp</id>
    <title>GHSA-mqxf-2998-c6cp — Craft Commerce is Vulnerable to Stored XSS while updating Order Status from Orders Table</title>
    <updated>2026-10-18T05:39:36.093603+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: craftcms/commerce</p>
<p>## Summary
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.</p>
<p>---
## Proof of Concept
### Required Permissions
- Admin access (to edit/create Order Statuses)</p>
<p>### Steps to Reproduce
1. Log in with an admin account
2. Navigate to **Commerce** → **Settings** → **Order Statuses**
3. Create a new order status
4. Set the **Name** field to:
```html
&lt;img src=x onerror="alert('Order Statuses XSS')"&gt;
```
5. Save the order status
6. Go to Commerce → Orders (make sure you placed any orders)
7. From the left panel, select any Order Status (e.g., New)
8. Select any order from the orders table → Click on the Gear Icon → then click "Update Order Status..."
9. Notice the XSS execution</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mqxf-2998-c6cp"/>
  </entry>
</feed>
