<?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>Mon, 05 Oct 2026 17:19:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-287526</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-287526</link>
      <description>EUVD-2026-287526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-287526</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3222</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3222</link>
      <description>&lt;p&gt;The WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the &amp;#39;location_id&amp;#39; parameter in all versions up to, and including, 4.9.1. This is due to the plugin&amp;#39;s database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the &amp;#39;location_id&amp;#39; parameter in all versions up to, and including, 4.9.1. This is due to the plugin&amp;#39;s database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3222</guid>
    </item>
    <item>
      <title>GHSA-4pfw-7fxf-mmv5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4pfw-7fxf-mmv5</link>
      <description>&lt;p&gt;The WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the &amp;#39;location_id&amp;#39; parameter in all versions up to, and including, 4.9.1. This is due to the plugin&amp;#39;s database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the &amp;#39;location_id&amp;#39; parameter in all versions up to, and including, 4.9.1. This is due to the plugin&amp;#39;s database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4pfw-7fxf-mmv5</guid>
    </item>
  </channel>
</rss>
