<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-20T18:05:03.542420+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-9979</id>
    <title>EUVD-2026-9979</title>
    <updated>2026-10-20T18:05:03.545709+00:00</updated>
    <content>EUVD-2026-9979</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-9979"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-48218</id>
    <title>fkie_cve-2023-48218</title>
    <updated>2026-10-20T18:05:03.545750+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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't have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-48218"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6h67-934r-82g7</id>
    <title>GHSA-6h67-934r-82g7 — Bypass of field access control in strapi-plugin-protected-populate</title>
    <updated>2026-10-20T18:05:03.545784+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: strapi-plugin-protected-populate</p>
<p>### 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't have access to.</p>
<p>### Patches
This issue has been patched in 1.3.4</p>
<p>### Workarounds
None</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6h67-934r-82g7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-48218</id>
    <title>gsd-2023-48218</title>
    <updated>2026-10-20T18:05:03.545812+00:00</updated>
    <content>gsd-2023-48218</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-48218"/>
  </entry>
</feed>
