Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-15300 critical CVSS 9.1

SQL Injection in GEO my WP (WordPress plugin) (CVE-2026-15300)

Summary

SQL injection in GEO my WP (WordPress plugin) (CVE-2026-15300). Data can be tampered with by attackers. Mitigation: upgrade to 4.5.5 or later.

Original description

The description as published by the source.

The GEO my WP plugin for WordPress was vulnerable to SQL Injection via the 'distance', 'lat', and 'lng' parameters in versions up to, and including, 4.5.4. The values were read from $_SERVER['QUERY_STRING'] via parse_str() (bypassing wp_magic_quotes, which does not cover $_SERVER), then passed through bare esc_sql() before being interpolated into unquoted numeric positions in the proximity-search query (HAVING/SELECT clause distance math, BETWEEN bounding-box pre-filter) built by gmw_locations_query() in plugins/posts-locator/includes/class-gmw-wp-query.php. Because esc_sql() only escapes string delimiters and these positions are numeric, payloads such as 1 OR SLEEP(3) survived sanitization. Fixed in 4.5.5 by adding an upstream is_numeric() guard that short-circuits the WHERE clause to AND 1 = 0 when either coordinate is non-numeric, and by replacing the three esc_sql() calls with (float) casts.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-15300 has been found in GEO my WP (WordPress plugin).
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade GEO my WP (WordPress plugin) to 4.5.5 or later.
If unsure, ask your IT team or search "GEO my WP (WordPress plugin) CVE-2026-15300" on the vendor's site.

CVE-2026-15300 (GEO my WP (WordPress plugin)) — CWE-89 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.5.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in GEO my WP (WordPress plugin).

📍 Affected scope

Check the vendor advisory for the affected versions of GEO my WP (WordPress plugin).

🔥 Severity

Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 4.5.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで GEO my WP (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade GEO my WP (WordPress plugin) to 4.5.5

    ステージング環境で 4.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details