CVE-2026-9757 HIGH

CVE-2026-9757: GEO my WP <= 4.5.5 - Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters

Vendor Ninjew
Product GEO my WP
Weakness CWE-89 · SQLi
Published May 30, 2026
Last update June 1, 2026
View on NVD All CVEs

CVSS base score

7.5/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

The GEO my WP plugin for WordPress is vulnerable to SQL Injection via the 'swlatlng' and 'nelatlng' parameters in all versions up to, and including, 4.5.5 The parameters are read from $_SERVER['QUERY_STRING'] via parse_str() (bypassing WordPress's wp_magic_quotes protection, which only covers $_POST/$_GET/$_COOKIE/$_REQUEST), then each is split on ',' via explode() and the resulting fragments are interpolated directly into a SQL BETWEEN clause in gmw_get_locations_within_boundaries_sql() without is_numeric() validation, (float) casting, esc_sql(), or $wpdb->prepare(). 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. Exploitation requires the site to host the Posts Locator search-results shortcode (`[gmw form="results" form_id=N]`) on a public page and to have at least one published post with an associated gmw_location row.

Explanation of Vulnerability in Simple Terms

02Summary

GEO my WP versions 4.5.5 and earlier contain a SQL injection vulnerability accessible over the network without authentication. An attacker can craft malicious input to read sensitive data from the site's database, including user credentials and private content. No user interaction is required to exploit this flaw.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site database, including user credentials and private information.

Potential impact on your site

04Site Impact

Attackers can extract user passwords, email addresses, and other confidential data stored in your database.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 30, 2026 CVE published
June 1, 2026 Record updated