<?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, 13 Nov 2026 14:13:52 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-10780</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-10780</link>
      <description>&lt;p&gt;The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied &amp;#39;id&amp;#39; attribute and outputting its post_content without verifying the post&amp;#39;s status (private, draft, pending) or the requesting user&amp;#39;s capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id=&amp;#34;X&amp;#34;] shortcode in their own content and previewing it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied &amp;#39;id&amp;#39; attribute and outputting its post_content without verifying the post&amp;#39;s status (private, draft, pending) or the requesting user&amp;#39;s capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id=&amp;#34;X&amp;#34;] shortcode in their own content and previewing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-10780</guid>
    </item>
    <item>
      <title>GHSA-3hxp-mvw5-v9p7</title>
      <link>https://db.gcve.eu/vuln/ghsa-3hxp-mvw5-v9p7</link>
      <description>&lt;p&gt;The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied &amp;#39;id&amp;#39; attribute and outputting its post_content without verifying the post&amp;#39;s status (private, draft, pending) or the requesting user&amp;#39;s capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id=&amp;#34;X&amp;#34;] shortcode in their own content and previewing it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied &amp;#39;id&amp;#39; attribute and outputting its post_content without verifying the post&amp;#39;s status (private, draft, pending) or the requesting user&amp;#39;s capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id=&amp;#34;X&amp;#34;] shortcode in their own content and previewing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-3hxp-mvw5-v9p7</guid>
    </item>
  </channel>
</rss>
