ninjew GEO my WP Plugin up to 4.5.4 on WordPress Proximity-Search Query class-gmw-wp-query.php gmw_locations_query distance/lat/lng sql injection

Summaryinfo

A vulnerability classified as critical has been found in ninjew GEO my WP Plugin up to 4.5.4. This impacts the function gmw_locations_query of the file plugins/posts-locator/includes/class-gmw-wp-query.php of the component Proximity-Search Query. Performing a manipulation of the argument distance/lat/lng results in sql injection. This vulnerability is reported as CVE-2026-15300. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in ninjew GEO my WP Plugin up to 4.5.4. This affects the function gmw_locations_query of the file plugins/posts-locator/includes/class-gmw-wp-query.php of the component Proximity-Search Query. The manipulation of the argument distance/lat/lng with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the 'distance', 'lat', and 'lng' parameters in versions up to, and including, 4.5.4. The values were read from $_SERVER['QUERY_STRING'] 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.

The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-15300 since 07/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:plugins/posts-locator/includes/class-gmw-wp-query.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 4.5.5 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• ninjew

Name

• GEO my WP Plugin

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion