<?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>Mon, 05 Oct 2026 20:05:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-0682 — Page Restrict &lt;= 2.5.5 - Protection Mechanism Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-0682</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sivel Page Restrict, theandystratton page_restrict&lt;/p&gt;
&lt;p&gt;The Page Restrict plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 2.5.5. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sivel Page Restrict, theandystratton page_restrict&lt;/p&gt;
&lt;p&gt;The Page Restrict plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 2.5.5. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-0682</guid>
    </item>
  </channel>
</rss>
