<?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>Tue, 20 Oct 2026 20:28:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-48218 — Strapi Protected Populate Plugin leaking fields if the request fields where empty or only fields selected where not pop…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-48218</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; strapi-community strapi-plugin-protected-populate&lt;/p&gt;
&lt;p&gt;The Strapi Protected Populate Plugin protects `get` endpoints from revealing too much information. Prior to version 1.3.4, users were able to bypass the field level security. Users who tried to populate something that they didn&amp;#39;t have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; strapi-community strapi-plugin-protected-populate&lt;/p&gt;
&lt;p&gt;The Strapi Protected Populate Plugin protects `get` endpoints from revealing too much information. Prior to version 1.3.4, users were able to bypass the field level security. Users who tried to populate something that they didn&amp;#39;t have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-48218</guid>
    </item>
  </channel>
</rss>
