<?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>Fri, 02 Oct 2026 20:32:22 +0000</lastBuildDate>
    <item>
      <title>BIT-wordpress-2026-3906 — WordPress 6.9 - 6.9.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Note Creation via REST API</title>
      <link>https://cve.radiocsirt.org/vuln/bit-wordpress-2026-3906</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: wordpress&lt;/p&gt;
&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: wordpress&lt;/p&gt;
&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-wordpress-2026-3906</guid>
    </item>
    <item>
      <title>EUVD-2026-275418</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275418</link>
      <description>EUVD-2026-275418</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275418</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3906</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3906</link>
      <description>&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3906</guid>
    </item>
    <item>
      <title>GHSA-6x83-fcf5-r65g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6x83-fcf5-r65g</link>
      <description>&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6x83-fcf5-r65g</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-3906</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-3906</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: wordpress, Ubuntu:18.04:LTS: wordpress, Ubuntu:20.04:LTS: wordpress, Ubuntu:22.04:LTS: wordpress, Ubuntu:24.04:LTS: wordpress, Ubuntu:25.10: wordpress, Ubuntu:26.04:LTS: wordpress&lt;/p&gt;
&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: wordpress, Ubuntu:18.04:LTS: wordpress, Ubuntu:20.04:LTS: wordpress, Ubuntu:22.04:LTS: wordpress, Ubuntu:24.04:LTS: wordpress, Ubuntu:25.10: wordpress, Ubuntu:26.04:LTS: wordpress&lt;/p&gt;
&lt;p&gt;WordPress core is vulnerable to unauthorized access in versions 6.9 through 6.9.1. The Notes feature (block-level collaboration annotations) was introduced in WordPress 6.9 to allow editorial comments directly on posts in the block editor. However, the REST API `create_item_permissions_check()` method in the comments controller did not verify that the authenticated user has `edit_post` permission on the target post when creating a note. This makes it possible for authenticated attackers with Subscriber-level access to create notes on any post, including posts authored by other users, private posts, and posts in any status.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-3906</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0684 — WordPress: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0684</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in WordPress potenziell ausnutzen, um Code auszuführen, Zugriffskontrollen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, DoS-Bedingungen auszulösen oder andere nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in WordPress potenziell ausnutzen, um Code auszuführen, Zugriffskontrollen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, DoS-Bedingungen auszulösen oder andere nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0684</guid>
    </item>
  </channel>
</rss>
