<?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>Sun, 18 Oct 2026 11:25:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-0679 — Fortis for WooCommerce &lt;= 1.2.0 - Missing Authorization to Unauthenticated Arbitrary Order Status Update to Paid via 'w…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-0679</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fortispay Fortis for WooCommerce&lt;/p&gt;
&lt;p&gt;The Fortis for WooCommerce plugin for WordPress is vulnerable to authorization bypass due to an inverted nonce check in the &amp;#39;check_fortis_notify_response&amp;#39; function in all versions up to, and including, 1.2.0. This makes it possible for unauthenticated attackers to update arbitrary WooCommerce order statuses to paid/processing/completed, effectively allowing them to mark orders as paid without payment.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fortispay Fortis for WooCommerce&lt;/p&gt;
&lt;p&gt;The Fortis for WooCommerce plugin for WordPress is vulnerable to authorization bypass due to an inverted nonce check in the &amp;#39;check_fortis_notify_response&amp;#39; function in all versions up to, and including, 1.2.0. This makes it possible for unauthenticated attackers to update arbitrary WooCommerce order statuses to paid/processing/completed, effectively allowing them to mark orders as paid without payment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-0679</guid>
    </item>
  </channel>
</rss>
