<?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>Tue, 06 Oct 2026 08:34:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-15647 — Brands for WooCommerce &lt;= 3.8.8 - Authenticated (Shop Manager+) Stored Cross-Site Scripting via 'br_brand_tooltip' Term…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-15647</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; berocket Brands for WooCommerce&lt;/p&gt;
&lt;p&gt;The Brands for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;br_brand_tooltip&amp;#39; Term Meta Field in all versions up to, and including, 3.8.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the payload is stored in term meta rather than post content, the WordPress unfiltered_html capability exception does not apply, meaning Shop Manager-level users — who normally lack unfiltered_html — can fully exploit this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; berocket Brands for WooCommerce&lt;/p&gt;
&lt;p&gt;The Brands for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;br_brand_tooltip&amp;#39; Term Meta Field in all versions up to, and including, 3.8.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the payload is stored in term meta rather than post content, the WordPress unfiltered_html capability exception does not apply, meaning Shop Manager-level users — who normally lack unfiltered_html — can fully exploit this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-15647</guid>
    </item>
  </channel>
</rss>
