<?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>Thu, 22 Oct 2026 16:39:59 +0000</lastBuildDate>
    <item>
      <title>cnvd-2026-05361</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-05361</link>
      <description>cnvd-2026-05361</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-05361</guid>
    </item>
    <item>
      <title>EUVD-2026-263996</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-263996</link>
      <description>EUVD-2026-263996</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-263996</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68400</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68400</link>
      <description>&lt;p&gt;ChurchCRM is an open-source church management system. A SQL Injection vulnerability exists in the legacy endpoint `/Reports/ConfirmReportEmail.php` in ChurchCRM prior to version 6.5.3. Although the feature was removed from the UI, the file remains deployed and reachable directly via URL. This is a classic case of *dead but reachable code*. Any authenticated user - including one with zero assigned permissions - can exploit SQL injection through the `familyId` parameter. Version 6.5.3 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ChurchCRM is an open-source church management system. A SQL Injection vulnerability exists in the legacy endpoint `/Reports/ConfirmReportEmail.php` in ChurchCRM prior to version 6.5.3. Although the feature was removed from the UI, the file remains deployed and reachable directly via URL. This is a classic case of *dead but reachable code*. Any authenticated user - including one with zero assigned permissions - can exploit SQL injection through the `familyId` parameter. Version 6.5.3 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68400</guid>
    </item>
  </channel>
</rss>
