<?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>Sun, 04 Oct 2026 08:52:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97660 — WPC Product Options for WooCommerce &lt;= 4.0.5 - Unauthenticated Stored Cross-Site Scripting via wpcpo-* Array Key via Mu…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97660</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpclever WPC Product Options for WooCommerce&lt;/p&gt;
&lt;p&gt;The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via wpcpo-* Array Key via Multipart Field Name in all versions up to, and including, 4.0.5 due to insufficient input sanitization and 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. This is exploitable via guest checkout without authentication because the malicious payload is embedded in a multipart Content-Disposition field name beginning with &amp;#39;wpcpo-&amp;#39;, which PHP&amp;#39;s RFC1867 parser preserves byte-for-byte and stores into order item meta.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpclever WPC Product Options for WooCommerce&lt;/p&gt;
&lt;p&gt;The WPC Product Options for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via wpcpo-* Array Key via Multipart Field Name in all versions up to, and including, 4.0.5 due to insufficient input sanitization and 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. This is exploitable via guest checkout without authentication because the malicious payload is embedded in a multipart Content-Disposition field name beginning with &amp;#39;wpcpo-&amp;#39;, which PHP&amp;#39;s RFC1867 parser preserves byte-for-byte and stores into order item meta.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97660</guid>
    </item>
  </channel>
</rss>
