<?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 12:36:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-2422 — WP Composer &lt;= 1.0.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'pbwp_raw_shortcode' Shortcode</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-2422</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ghozylab WP Composer – The Easiest Page Builder&lt;/p&gt;
&lt;p&gt;The WP Composer – The Easiest Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;pbwp_raw_shortcode&amp;#39; shortcode in all versions up to, and including, 1.0.5. This is due to the shortcode handler decoding Base64-encoded content and outputting it directly without any sanitization or 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 Base64 encoding allows the payload to bypass WordPress&amp;#39;s KSES content filtering at save time, since the encoded string contains no harmful HTML characters.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ghozylab WP Composer – The Easiest Page Builder&lt;/p&gt;
&lt;p&gt;The WP Composer – The Easiest Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;pbwp_raw_shortcode&amp;#39; shortcode in all versions up to, and including, 1.0.5. This is due to the shortcode handler decoding Base64-encoded content and outputting it directly without any sanitization or 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 Base64 encoding allows the payload to bypass WordPress&amp;#39;s KSES content filtering at save time, since the encoded string contains no harmful HTML characters.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-2422</guid>
    </item>
  </channel>
</rss>
