CVE-2026-9757: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ninjew GEO my WP
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.
AI Analysis
Technical Summary
CVE-2026-9757 is an SQL Injection vulnerability in the GEO my WP WordPress plugin affecting all versions up to 4.5.5. The issue arises because the 'swlatlng' and 'nelatlng' parameters are extracted from $_SERVER['QUERY_STRING'] using parse_str(), bypassing WordPress's wp_magic_quotes protections. These parameters are then split and directly interpolated into a SQL BETWEEN clause in the gmw_get_locations_within_boundaries_sql() function without numeric validation, casting, escaping, or prepared statements. This improper neutralization of special elements (CWE-89) enables unauthenticated attackers to append malicious SQL code to queries, risking unauthorized data disclosure. Exploitation requires the presence of a public page with the Posts Locator shortcode and at least one published post with location data.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform SQL Injection attacks, enabling them to extract sensitive information from the database. The vulnerability does not affect data integrity or availability directly but compromises confidentiality. The attack surface requires specific plugin usage conditions, including a public page with the Posts Locator shortcode and existing location data. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should consider removing or disabling the Posts Locator shortcode on public pages or restricting access to affected pages to trusted users. Monitoring for unusual database queries related to these parameters may help detect exploitation attempts. Avoid relying on WordPress's wp_magic_quotes for query string parameters, and consider applying manual input validation or using a web application firewall to block suspicious requests targeting 'swlatlng' and 'nelatlng' parameters.
CVE-2026-9757: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ninjew GEO my WP
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.
CVSS v3.1
Score 7.5high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9757 is an SQL Injection vulnerability in the GEO my WP WordPress plugin affecting all versions up to 4.5.5. The issue arises because the 'swlatlng' and 'nelatlng' parameters are extracted from $_SERVER['QUERY_STRING'] using parse_str(), bypassing WordPress's wp_magic_quotes protections. These parameters are then split and directly interpolated into a SQL BETWEEN clause in the gmw_get_locations_within_boundaries_sql() function without numeric validation, casting, escaping, or prepared statements. This improper neutralization of special elements (CWE-89) enables unauthenticated attackers to append malicious SQL code to queries, risking unauthorized data disclosure. Exploitation requires the presence of a public page with the Posts Locator shortcode and at least one published post with location data.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform SQL Injection attacks, enabling them to extract sensitive information from the database. The vulnerability does not affect data integrity or availability directly but compromises confidentiality. The attack surface requires specific plugin usage conditions, including a public page with the Posts Locator shortcode and existing location data. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should consider removing or disabling the Posts Locator shortcode on public pages or restricting access to affected pages to trusted users. Monitoring for unusual database queries related to these parameters may help detect exploitation attempts. Avoid relying on WordPress's wp_magic_quotes for query string parameters, and consider applying manual input validation or using a web application firewall to block suspicious requests targeting 'swlatlng' and 'nelatlng' parameters.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-27T18:00:12.927Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1ab2aee29bf47b5015dfbd
Added to database: 5/30/2026, 9:49:34 AM
Last enriched: 5/30/2026, 10:03:27 AM
Last updated: 5/31/2026, 4:07:24 AM
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.