<?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>Mon, 05 Oct 2026 15:09:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-331048</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-331048</link>
      <description>EUVD-2026-331048</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-331048</guid>
    </item>
    <item>
      <title>fkie_cve-2026-12432</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-12432</link>
      <description>&lt;p&gt;The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this-&amp;gt;db-&amp;gt;updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site&amp;#39;s database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this-&amp;gt;db-&amp;gt;updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site&amp;#39;s database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-12432</guid>
    </item>
    <item>
      <title>GHSA-26qv-fwp4-4p47</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-26qv-fwp4-4p47</link>
      <description>&lt;p&gt;The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this-&amp;gt;db-&amp;gt;updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site&amp;#39;s database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this-&amp;gt;db-&amp;gt;updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site&amp;#39;s database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-26qv-fwp4-4p47</guid>
    </item>
  </channel>
</rss>
