# 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.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-823p-x8f9-wj7r

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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.

## Is CVE-2026-9757 being exploited?

There is no known exploitation of CVE-2026-9757 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9757 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-9757 in the wild and no public exploit code.

Affected product: ninjew GEO my WP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9757/ (Markdown: https://insights.sbomify.com/CVE-2026-9757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9757
- OSV: https://osv.dev/vulnerability/CVE-2026-9757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9757/
Summaries are generated and may contain mistakes; the official description above is the record.