PT-2026-45090 · Ninjew · Geo My Wp
Naoya Takahashi
·
Published
2026-05-30
·
Updated
2026-05-30
·
CVE-2026-9757
CVSS v3.1
7.5
High
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
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.Fix
SQL injection
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Geo My Wp