<?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-05T18:06:42.074259+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-211572</id>
    <title>EUVD-2026-211572</title>
    <updated>2026-10-05T18:06:42.077592+00:00</updated>
    <content>EUVD-2026-211572</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-211572"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-29927</id>
    <title>fkie_cve-2023-29927</title>
    <updated>2026-10-05T18:06:42.077636+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Versions of Sage 300 through 2022 implement role-based access controls that are only enforced client-side. Low-privileged Sage users, particularly those on a workstation setup in the "Windows Peer-to-Peer Network" or "Client Server Network" Sage 300 configurations, could recover the SQL connection strings being used by Sage 300 and interact directly with the underlying database(s) to create, update, and delete all company records, bypassing the program’s role-based access controls.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-29927"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qw6r-773c-w64h</id>
    <title>GHSA-qw6r-773c-w64h</title>
    <updated>2026-10-05T18:06:42.077684+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Versions of Sage 300 through 2022 implement role-based access controls that are only enforced client-side. Low-privileged Sage users, particularly those on a workstation setup in the "Windows Peer-to-Peer Network" or "Client Server Network" Sage 300 configurations, could recover the SQL connection strings being used by Sage 300 and interact directly with the underlying database(s) to create, update, and delete all company records, bypassing the program’s role-based access controls.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qw6r-773c-w64h"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-29927</id>
    <title>gsd-2023-29927</title>
    <updated>2026-10-05T18:06:42.077717+00:00</updated>
    <content>gsd-2023-29927</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-29927"/>
  </entry>
</feed>
