dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-9757

HIGH · 7.5 CVSS v3.1 Published 2026-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GEO my WP plugin for WordPress up to version 4.5.5 contains a SQL Injection vulnerability in the gmw_get_locations_within_boundaries_sql() function. The 'swlatlng' and 'nelatlng' parameters are read from $_SERVER['QUERY_STRING'] via parse_str(), which bypasses WordPress's built-in magic quotes protection that only covers $_POST/$_GET/$_COOKIE/$_REQUEST. These parameters are split on ',' using explode() and the resulting values are directly interpolated into a SQL BETWEEN clause without any validation (is_numeric(), (float) casting) or sanitization (esc_sql(), $wpdb->prepare()). This allows unauthenticated attackers to inject arbitrary SQL queries.

MitigationUpdate to a patched version of GEO my WP that implements proper input validation and uses $wpdb->prepare() or esc_sql() for all database queries. Until a patch is available, disable the Posts Locator shortcode from public pages or restrict access to authenticated users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GEO my WP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GEO my WP'. Alternatively, check /wp-content/plugins/geo-my-wp/ directory exists and contains plugin files.
    Affected if The plugin is not installed or directory does not exist - not affected.
  2. Identify installed version
    Check the plugin version in the plugin header at /wp-content/plugins/geo-my-wp/geo-my-wp.php, or view the plugin in WordPress admin which displays the version number.
    Affected if Version is less than 4.5.6 - likely affected. Version 4.5.6 or later includes the fix.
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm GEO my WP shows as 'Active'. Only active plugins process requests and are vulnerable.
    Affected if Plugin is inactive - not affected when inactive.
  4. Check for vulnerable code pattern
    Search plugin files for 'swlatlng' or 'nelatlng' parameters. Look for direct use of parse_str($_SERVER['QUERY_STRING']) followed by SQL queries without $wpdb->prepare(). Common locations: plugin shortcode or AJAX handlers.
    Affected if Vulnerable code pattern exists without $wpdb->prepare() - confirmed vulnerable.

User is affected if GEO my WP plugin is installed, active, and version is below 4.5.6, with vulnerable SQL query code present that directly uses query string parameters in BETWEEN clauses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of GEO my WP that implements proper input validation and uses $wpdb->prepare() or esc_sql() for all database queries. Until a patch is available, disable the Posts Locator shortcode from public pages or restrict access to authenticated users only.

Recommended fix High confidence

GEO my WP version 4.5.6

  1. Upgrade GEO my WP plugin to version 4.5.6 or later
  2. Verify the upgrade was successful by checking the plugin version in WordPress admin > Plugins
  3. Test the Posts Locator search functionality to confirm the shortcode `[gmw form="results" form_id=N]` still works correctly
  4. Confirm no SQL injection warnings in server logs after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9757 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data