<?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, 09 Oct 2026 06:09:34 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-286866</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-286866</link>
      <description>EUVD-2026-286866</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-286866</guid>
    </item>
    <item>
      <title>fkie_cve-2024-0681</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-0681</link>
      <description>&lt;p&gt;The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-0681</guid>
    </item>
    <item>
      <title>GHSA-ccwc-7pw8-r82c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ccwc-7pw8-r82c</link>
      <description>&lt;p&gt;The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ccwc-7pw8-r82c</guid>
    </item>
    <item>
      <title>gsd-2024-0681</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-0681</link>
      <description>gsd-2024-0681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-0681</guid>
    </item>
  </channel>
</rss>
