<?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>Tue, 06 Oct 2026 11:20:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-15300 — GEO my WP &lt;= 4.5.4 - Unauthenticated SQL Injection via 'distance' / 'lat' / 'lng' Parameters</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-15300</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ninjew GEO my WP&lt;/p&gt;
&lt;p&gt;The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the &amp;#39;distance&amp;#39;, &amp;#39;lat&amp;#39;, and &amp;#39;lng&amp;#39; parameters in versions up to, and including, 4.5.4. The values were read from $_SERVER[&amp;#39;QUERY_STRING&amp;#39;] via parse_str() (bypassing wp_magic_quotes, which does not cover $_SERVER), then passed through bare esc_sql() before being interpolated into unquoted numeric positions in the proximity-search query (HAVING/SELECT clause distance math, BETWEEN bounding-box pre-filter) built by gmw_locations_query() in plugins/posts-locator/includes/class-gmw-wp-query.php. Because esc_sql() only escapes string delimiters and these positions are numeric, payloads such as `1 OR SLEEP(3)` survived sanitization. Fixed in 4.5.5 by adding an upstream is_numeric() guard that short-circuits the WHERE clause to `AND 1 = 0` when either coordinate is non-numeric, and by replacing the three esc_sql() calls with (float) casts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ninjew GEO my WP&lt;/p&gt;
&lt;p&gt;The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the &amp;#39;distance&amp;#39;, &amp;#39;lat&amp;#39;, and &amp;#39;lng&amp;#39; parameters in versions up to, and including, 4.5.4. The values were read from $_SERVER[&amp;#39;QUERY_STRING&amp;#39;] via parse_str() (bypassing wp_magic_quotes, which does not cover $_SERVER), then passed through bare esc_sql() before being interpolated into unquoted numeric positions in the proximity-search query (HAVING/SELECT clause distance math, BETWEEN bounding-box pre-filter) built by gmw_locations_query() in plugins/posts-locator/includes/class-gmw-wp-query.php. Because esc_sql() only escapes string delimiters and these positions are numeric, payloads such as `1 OR SLEEP(3)` survived sanitization. Fixed in 4.5.5 by adding an upstream is_numeric() guard that short-circuits the WHERE clause to `AND 1 = 0` when either coordinate is non-numeric, and by replacing the three esc_sql() calls with (float) casts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-15300</guid>
    </item>
  </channel>
</rss>
