<?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>Mon, 05 Oct 2026 16:44:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-75966 — Podlove Podcast Publisher &lt;= 4.5.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'episode_contributor[…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-75966</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; eteubert Podlove Podcast Publisher&lt;/p&gt;
&lt;p&gt;The Podlove Podcast Publisher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;episode_contributor[..][..][comment]&amp;#39; Parameter in all versions up to, and including, 4.5.5 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 contributor comment is stored in a plugin-managed custom table, bypassing WordPress core&amp;#39;s wp_kses_post filter, and the save_post hook fires without a nonce check, meaning any user who can edit posts can exploit this without further preconditions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; eteubert Podlove Podcast Publisher&lt;/p&gt;
&lt;p&gt;The Podlove Podcast Publisher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;episode_contributor[..][..][comment]&amp;#39; Parameter in all versions up to, and including, 4.5.5 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 contributor comment is stored in a plugin-managed custom table, bypassing WordPress core&amp;#39;s wp_kses_post filter, and the save_post hook fires without a nonce check, meaning any user who can edit posts can exploit this without further preconditions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-75966</guid>
    </item>
  </channel>
</rss>
