<?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://db.gcve.eu</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>Fri, 02 Oct 2026 03:06:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-101925 — bbp style pack &lt;= 6.4.8 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Author Display Name</title>
      <link>https://db.gcve.eu/vuln/cve-2026-101925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; robin-w bbp style pack&lt;/p&gt;
&lt;p&gt;The bbp style pack plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;display_name (via /wp-admin/profile.php) + bbp_reply_content (via bbPress reply form)&amp;#39; parameter in all versions up to, and including, 6.4.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the attacker to wrap their crafted reply in a &amp;amp;lt;pre&amp;amp;gt; block, which prevents WordPress&amp;#39;s wpautop/wptexturize processors from converting straight double quotes in the stored display name into typographic curly-quote entities that would otherwise neutralize the attribute-injection.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; robin-w bbp style pack&lt;/p&gt;
&lt;p&gt;The bbp style pack plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;display_name (via /wp-admin/profile.php) + bbp_reply_content (via bbPress reply form)&amp;#39; parameter in all versions up to, and including, 6.4.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the attacker to wrap their crafted reply in a &amp;amp;lt;pre&amp;amp;gt; block, which prevents WordPress&amp;#39;s wpautop/wptexturize processors from converting straight double quotes in the stored display name into typographic curly-quote entities that would otherwise neutralize the attribute-injection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-101925</guid>
    </item>
  </channel>
</rss>
