<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 19:46:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-323667</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323667</link>
      <description>EUVD-2026-323667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323667</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47740</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47740</link>
      <description>&lt;p&gt;Shopper is a Headless e-commerce Admin Panel. Prior to 2.8.0, Multiple Filament actions on the admin Order detail and Order shipments table were callable by an authenticated low-privilege user without the permission required to mutate orders. The order detail actions cancel, mark paid, mark complete, capture payment, archive, and start processing were callable with the read-only read_orders permission and did not require edit_orders. capturePayment could trigger an actual PSP capture (real funds movement). The order shipments table actions mark delivered and edit tracking were callable with the read-only browse_orders permission. A user with read access to orders could therefore alter the lifecycle of every order in the panel and trigger real-world payment captures. This vulnerability is fixed in 2.8.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Shopper is a Headless e-commerce Admin Panel. Prior to 2.8.0, Multiple Filament actions on the admin Order detail and Order shipments table were callable by an authenticated low-privilege user without the permission required to mutate orders. The order detail actions cancel, mark paid, mark complete, capture payment, archive, and start processing were callable with the read-only read_orders permission and did not require edit_orders. capturePayment could trigger an actual PSP capture (real funds movement). The order shipments table actions mark delivered and edit tracking were callable with the read-only browse_orders permission. A user with read access to orders could therefore alter the lifecycle of every order in the panel and trigger real-world payment captures. This vulnerability is fixed in 2.8.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47740</guid>
    </item>
    <item>
      <title>GHSA-f946-9qp6-vgch — shopper/framework: Authorization bypass in multiple Livewire admin components</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f946-9qp6-vgch</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopper/framework&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Multiple Livewire components in the admin panel allowed an authenticated low-privilege user to mutate data without the required permission:&lt;/p&gt;
&lt;p&gt;- Order detail Filament actions (cancel, mark paid, mark complete, capture payment, archive, start processing) were callable with `read_orders` only and did not require `edit_orders`. `capturePayment` could trigger an actual PSP capture.
- Order shipments table actions (mark delivered, edit tracking) were callable with `browse_orders` only.
- Sub-form Livewire components for products (Edit, Inventory, Seo, Shipping, Files) had no authorization on `store()`, so any authenticated panel user could mutate product data without `edit_products`.
- `Settings/Team/Index` had no `mount()` authorization at all — any authenticated user could create roles and delete other users.
- `Settings/Team/RolePermission` gated its write actions on the read-only `view_users` permission, allowing privilege escalation via the RBAC system itself.
- `PaymentMethods`, `Currencies`, `Carriers` table toggles and per-record actions had no per-action permission check.
- `Customers/Create::store()` re-passed a Hidden `_password` form field into the create payload.&lt;/p&gt;
&lt;p&gt;Several public Eloquent model properties on Livewire components were not `#[Locked]`, allowing client-side ID tampering.&lt;/p&gt;
&lt;p&gt;A stored XSS surface existed on the product barcode field, which is rendered through `DNS1DFacade::getBarcodeHTML()` with `{!! !!}`.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `v2.8.0`. Upgrade via:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopper/framework&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Multiple Livewire components in the admin panel allowed an authenticated low-privilege user to mutate data without the required permission:&lt;/p&gt;
&lt;p&gt;- Order detail Filament actions (cancel, mark paid, mark complete, capture payment, archive, start processing) were callable with `read_orders` only and did not require `edit_orders`. `capturePayment` could trigger an actual PSP capture.
- Order shipments table actions (mark delivered, edit tracking) were callable with `browse_orders` only.
- Sub-form Livewire components for products (Edit, Inventory, Seo, Shipping, Files) had no authorization on `store()`, so any authenticated panel user could mutate product data without `edit_products`.
- `Settings/Team/Index` had no `mount()` authorization at all — any authenticated user could create roles and delete other users.
- `Settings/Team/RolePermission` gated its write actions on the read-only `view_users` permission, allowing privilege escalation via the RBAC system itself.
- `PaymentMethods`, `Currencies`, `Carriers` table toggles and per-record actions had no per-action permission check.
- `Customers/Create::store()` re-passed a Hidden `_password` form field into the create payload.&lt;/p&gt;
&lt;p&gt;Several public Eloquent model properties on Livewire components were not `#[Locked]`, allowing client-side ID tampering.&lt;/p&gt;
&lt;p&gt;A stored XSS surface existed on the product barcode field, which is rendered through `DNS1DFacade::getBarcodeHTML()` with `{!! !!}`.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `v2.8.0`. Upgrade via:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f946-9qp6-vgch</guid>
    </item>
  </channel>
</rss>
