<?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>Thu, 08 Oct 2026 10:17:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-4334 — Shariff Wrapper &lt;= 4.6.20 - Authenticated (Contributor+) Cross-Site Scripting</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-4334</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 3uu Shariff Wrapper&lt;/p&gt;
&lt;p&gt;The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;headline&amp;#39; parameter in the [shariff] shortcode in all versions up to, and including, 4.6.20 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability occurs because the plugin uses a custom wp_kses implementation with permissive allowed HTML tags, and then performs a str_replace operation that injects HTML after sanitization, allowing event handlers to be introduced through the %total placeholder in the style attribute.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 3uu Shariff Wrapper&lt;/p&gt;
&lt;p&gt;The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;headline&amp;#39; parameter in the [shariff] shortcode in all versions up to, and including, 4.6.20 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability occurs because the plugin uses a custom wp_kses implementation with permissive allowed HTML tags, and then performs a str_replace operation that injects HTML after sanitization, allowing event handlers to be introduced through the %total placeholder in the style attribute.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-4334</guid>
    </item>
  </channel>
</rss>
