CVE-2026-9757 GEO my WP <= 4.5.5 - Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters
Unauthenticated attackers can extract sensitive database information via SQL injection in the GEO my WP WordPress plugin when specific shortcodes are active.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-9757?
CVE-2026-9757 is a high-severity SQL injection vulnerability in ninjew GEO my WP, published on 30 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-89
Which versions are affected by CVE-2026-9757?
How do I fix CVE-2026-9757?
No fix has been published for CVE-2026-9757 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-9757 being exploited?
There is no known exploitation of CVE-2026-9757 in the wild and no public exploit code.
Sources
Also known as GHSA-823p-x8f9-wj7r.