Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-15300 – Unauthenticated SQL Injection – GEO my WP WordPress Plugin ≤ 4.5.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-15300 is a critical unauthenticated SQL Injection vulnerability in the GEO my WP WordPress plugin, affecting all versions up to and including 4.5.4, with a CVSS v3.1 base score of 9.1. The flaw allows any remote, unauthenticated attacker to inject arbitrary SQL into the WordPress database by manipulating proximity-search query parameters, requiring no credentials and no user interaction. A patch is available in version 4.5.5.

Technical details

  • Root cause: The distance, lat, and lng URL parameters are read directly from $_SERVER['QUERY_STRING'] via PHP’s parse_str() function. This input path bypasses WordPress’s wp_magic_quotes mechanism, which does not cover the $_SERVER superglobal. The values are subsequently passed through esc_sql() — which only escapes string delimiter characters — before being interpolated into unquoted numeric positions in the proximity-search SQL query constructed by gmw_locations_query() in plugins/posts-locator/includes/class-gmw-wp-query.php.
  • Trigger conditions: The vulnerability is exploitable on any site with a public-facing page using the Posts Locator proximity-search shortcode — the primary function of this plugin. An attacker sends a crafted HTTP request to that page with a malicious value in the distance, lat, or lng query parameter.
  • Attack vector: Unauthenticated, fully network-based; no account, session, or browser interaction required.
  • Impact: Because the injected values land in numeric positions (HAVING/SELECT clause distance calculations and BETWEEN bounding-box pre-filter), payloads such as 1 OR SLEEP(3) survive esc_sql() sanitization and are executed directly by the database engine. The CVSS impact dimensions are High Integrity and High Availability, enabling an attacker to manipulate or destroy WordPress database records and trigger denial-of-service conditions against the database layer.

Affected software

  • GEO my WP WordPress plugin — all versions from initial release through 4.5.4 (inclusive)

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the GEO my WP plugin to version 4.5.5 or later. Version 4.5.5 addresses the vulnerability by introducing an upstream is_numeric() guard that short-circuits the WHERE clause to AND 1 = 0 when any coordinate value is non-numeric, and by replacing the three vulnerable esc_sql() calls with explicit (float) casts.
  • If immediate patching is not possible: Restrict public access to pages containing the Posts Locator proximity-search shortcode, or apply a web application firewall rule to reject requests that pass non-numeric values in the distance, lat, or lng query parameters.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge