<?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://vulnerability.circl.lu</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, 01 Oct 2026 19:38:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-15002 — Autopay &lt;= 5.0.0 - Unauthenticated Stored Cross-Site Scripting via 'bm_woocommerce_css_editor_content' Parameter</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-15002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bluemediapl Autopay&lt;/p&gt;
&lt;p&gt;The Platnosci Online Blue Media (Autopay) plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.0 via the &amp;#39;bm_woocommerce_css_editor_content&amp;#39; POST parameter. This is due to the Css_Editor::handle_save() method being wired to the WordPress &amp;#39;init&amp;#39; hook by Settings_Manager::init_once() with no capability check, no nonce verification, and no sanitization on the input — the raw $_POST value is written to the &amp;#39;woocommerce_bluemedia_settings&amp;#39; option via update_option(), then later echoed directly inside a &amp;lt;style&amp;gt; block on the WooCommerce checkout page by Css_Frontend::print_to_wp_head() with no output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page (the checkout page).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bluemediapl Autopay&lt;/p&gt;
&lt;p&gt;The Platnosci Online Blue Media (Autopay) plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.0 via the &amp;#39;bm_woocommerce_css_editor_content&amp;#39; POST parameter. This is due to the Css_Editor::handle_save() method being wired to the WordPress &amp;#39;init&amp;#39; hook by Settings_Manager::init_once() with no capability check, no nonce verification, and no sanitization on the input — the raw $_POST value is written to the &amp;#39;woocommerce_bluemedia_settings&amp;#39; option via update_option(), then later echoed directly inside a &amp;lt;style&amp;gt; block on the WooCommerce checkout page by Css_Frontend::print_to_wp_head() with no output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page (the checkout page).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-15002</guid>
    </item>
  </channel>
</rss>
