<?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 18:05:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-9979</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-9979</link>
      <description>EUVD-2026-9979</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-9979</guid>
    </item>
    <item>
      <title>fkie_cve-2023-48218</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-48218</link>
      <description>&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;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/fkie_cve-2023-48218</guid>
    </item>
    <item>
      <title>GHSA-6h67-934r-82g7 — Bypass of field access control in strapi-plugin-protected-populate</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6h67-934r-82g7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: strapi-plugin-protected-populate&lt;/p&gt;
&lt;p&gt;### Impact
Users are able to bypass the field level security. This means fields that they where not allowed to populate could be populated anyway even in the event that they tried to populate something that they don&amp;#39;t have access to.&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been patched in 1.3.4&lt;/p&gt;
&lt;p&gt;### Workarounds
None&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: strapi-plugin-protected-populate&lt;/p&gt;
&lt;p&gt;### Impact
Users are able to bypass the field level security. This means fields that they where not allowed to populate could be populated anyway even in the event that they tried to populate something that they don&amp;#39;t have access to.&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been patched in 1.3.4&lt;/p&gt;
&lt;p&gt;### Workarounds
None&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6h67-934r-82g7</guid>
    </item>
    <item>
      <title>gsd-2023-48218</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-48218</link>
      <description>gsd-2023-48218</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-48218</guid>
    </item>
  </channel>
</rss>
