<?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>Tue, 03 Nov 2026 18:06:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-116520 — PPWP &lt;= 1.9.26 - Unauthenticated Stored Cross-Site Scripting via '[ppwp]' Shortcode 'desc_below_form' Attribute via Pla…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-116520</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; buildwps PPWP – Password Protect Pages&lt;/p&gt;
&lt;p&gt;The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;comment / shortcode attribute desc_below_form (and placeholder as the marker-smuggling helper)&amp;#39; parameter in all versions up to, and including, 1.9.26 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because WordPress&amp;#39;s comment_content filter leaves bare shortcode text (containing no HTML tags) untouched, and the comment_whitelist setting auto-approves subsequent comments from a previously approved name and email without administrator intervention.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; buildwps PPWP – Password Protect Pages&lt;/p&gt;
&lt;p&gt;The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;comment / shortcode attribute desc_below_form (and placeholder as the marker-smuggling helper)&amp;#39; parameter in all versions up to, and including, 1.9.26 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because WordPress&amp;#39;s comment_content filter leaves bare shortcode text (containing no HTML tags) untouched, and the comment_whitelist setting auto-approves subsequent comments from a previously approved name and email without administrator intervention.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-116520</guid>
    </item>
  </channel>
</rss>
