<?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 21:00:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-57857 — Flow Payment Plugin for WordPress Reflected Cross-Site Scripting via error_message Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-57857</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Flow Payment&lt;/p&gt;
&lt;p&gt;The Flow Payment plugin for WordPress (flow.cl) version 3.0.8 is vulnerable to reflected cross-site scripting on the WooCommerce checkout page. When the plugin handles an order cancellation, the error_message GET parameter is passed directly to wc_add_notice() in flowpayment-fl.php (lines 57-58) without input sanitization (for example sanitize_text_field()) or output escaping (for example esc_html()) before being rendered in the checkout notice HTML. An unauthenticated attacker can craft a URL containing a JavaScript payload in the error_message parameter (for example /checkout/?add-to-cart={product-id}&amp;amp;cancel_order=true&amp;amp;error_message={payload}); when a victim with an active WooCommerce checkout session follows the link, the payload executes in the victim&amp;#39;s browser in the origin of the WordPress site.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Flow Payment&lt;/p&gt;
&lt;p&gt;The Flow Payment plugin for WordPress (flow.cl) version 3.0.8 is vulnerable to reflected cross-site scripting on the WooCommerce checkout page. When the plugin handles an order cancellation, the error_message GET parameter is passed directly to wc_add_notice() in flowpayment-fl.php (lines 57-58) without input sanitization (for example sanitize_text_field()) or output escaping (for example esc_html()) before being rendered in the checkout notice HTML. An unauthenticated attacker can craft a URL containing a JavaScript payload in the error_message parameter (for example /checkout/?add-to-cart={product-id}&amp;amp;cancel_order=true&amp;amp;error_message={payload}); when a victim with an active WooCommerce checkout session follows the link, the payload executes in the victim&amp;#39;s browser in the origin of the WordPress site.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-57857</guid>
    </item>
  </channel>
</rss>
