<?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>Sun, 18 Oct 2026 00:32:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276302</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276302</link>
      <description>EUVD-2026-276302</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276302</guid>
    </item>
    <item>
      <title>fkie_cve-2026-30881</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-30881</link>
      <description>&lt;p&gt;Chamilo LMS is a learning management system. Version 1.11.34 and prior contains a SQL Injection vulnerability in the statistics AJAX endpoint. The parameters date_start and date_end from $_REQUEST are embedded directly into a raw SQL string without proper sanitization. Although Database::escape_string() is called downstream, its output is immediately neutralized by str_replace(&amp;#34;\&amp;#39;&amp;#34;, &amp;#34;&amp;#39;&amp;#34;, ...), which restores any injected single quotes — effectively bypassing the escaping mechanism entirely. This allows an authenticated attacker to inject arbitrary SQL statements into the database query, enabling blind time-based and conditional data extraction. This issue has been patched in version 1.11.36.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Chamilo LMS is a learning management system. Version 1.11.34 and prior contains a SQL Injection vulnerability in the statistics AJAX endpoint. The parameters date_start and date_end from $_REQUEST are embedded directly into a raw SQL string without proper sanitization. Although Database::escape_string() is called downstream, its output is immediately neutralized by str_replace(&amp;#34;\&amp;#39;&amp;#34;, &amp;#34;&amp;#39;&amp;#34;, ...), which restores any injected single quotes — effectively bypassing the escaping mechanism entirely. This allows an authenticated attacker to inject arbitrary SQL statements into the database query, enabling blind time-based and conditional data extraction. This issue has been patched in version 1.11.36.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-30881</guid>
    </item>
  </channel>
</rss>
