Vulnerabilities and security researches forgeo-my-wp geo-my-wp

Direction: ascending

Jun 07, 2024

GEO my WordPress # CVE-2024-32097

CVE, Research URL: CVE-2024-32097
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Apr 15, 2024
Research Description: Cross-Site Request Forgery (CSRF) vulnerability in Eyal Fitoussi GEO my WordPress.This issue affects GEO my WordPress: from n/a through 4.1.
Affected versions: max 4.2.
Status: vulnerable

GEO my WordPress # CVE-2023-52134

CVE, Research URL: CVE-2023-52134
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Dec 31, 2023
Research Description: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Eyal Fitoussi GEO my WordPress.This issue affects GEO my WordPress: from n/a through 4.0.2.
Affected versions: max 4.0.3.
Status: vulnerable

GEO my WordPress # CVE-2023-5467

CVE, Research URL: CVE-2023-5467
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Oct 10, 2023
Research Description: The GEO my WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcodes in versions up to, and including, 4.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Affected versions: max 4.0.1.
Status: vulnerable

Aug 21, 2024

GEO my WordPress # CVE-2024-6330

CVE, Research URL: CVE-2024-6330
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Aug 19, 2024
Research Description: The GEO my WP WordPress plugin before 4.5.0.2 does not prevent unauthenticated attackers from including arbitrary files in PHP's execution context, which leads to Remote Code Execution.
Affected versions: max 4.5.0.2.
Status: vulnerable

Sep 28, 2024

GEO my WordPress # CVE-2024-47327

CVE, Research URL: CVE-2024-47327
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Oct 06, 2024
Research Description: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Eyal Fitoussi GEO my WordPress geo-my-wp allows Reflected XSS.This issue affects GEO my WordPress: from n/a through <= 4.5.0.3.
Affected versions: max 4.5.0.4.
Status: vulnerable

Nov 24, 2024

GEO my WordPress # CVE-2024-9422

CVE, Research URL: CVE-2024-9422
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Nov 22, 2024
Research Description: The GEO my WP WordPress plugin before 4.5, gmw-premium-settings WordPress plugin before 3.1 does not sufficiently validate files to be uploaded, which could allow attackers to upload arbitrary files such as PHP on the server.
Affected versions: Min 4.0, max 4.5.
Status: vulnerable

Dec 15, 2024

GEO my WordPress # CVE-2024-54326

CVE, Research URL: CVE-2024-54326
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Dec 13, 2024
Research Description: Missing Authorization vulnerability in Eyal Fitoussi GEO my WordPress geo-my-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GEO my WordPress: from n/a through <= 4.5.0.4.
Affected versions: max 4.5.1.
Status: vulnerable

Jun 01, 2026

GEO my WordPress # CVE-2026-9757

CVE, Research URL: CVE-2026-9757
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: May 30, 2026
Research 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.
Affected versions: max 4.5.5.1.
Status: vulnerable

Jun 16, 2026

GEO my WordPress # dcb0a98411557b7f12c0c1b5e00d526e7b90c21d

CVE, Research URL: dcb0a98411557b7f12c0c1b5e00d526e7b90c21d
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: May 27, 2026
Research Description: GEO my WP [geo-my-wp] < 4.5.5 GEO my WP <= 4.5.4 - Unauthenticated SQL Injection via 'distance' / 'lat' / 'lng' Parameters 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.
Affected versions: max 4.5.5.
Status: vulnerable

GEO my WordPress # feb463bc85fffe217d0d7b7fa9c331c6cdf5f048

CVE, Research URL: feb463bc85fffe217d0d7b7fa9c331c6cdf5f048
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: May 28, 2026
Research Description: GEO my WP [geo-my-wp] < 4.5.5 GEO my WP <= 4.5.4 - Unauthenticated SQL Injection The GEO my WP plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 4.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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.
Affected versions: max 4.5.5.
Status: vulnerable

Jul 12, 2026

GEO my WordPress # CVE-2026-15300

CVE, Research URL: CVE-2026-15300
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Jul 10, 2026
Research Description: 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.
Affected versions: max 4.5.5.
Status: vulnerable

Aug 04, 2026

GEO my WordPress # CVE-2026-15260

CVE, Research URL: CVE-2026-15260
Home page URL: Security reports for GEO my WordPress
Application: GEO my WordPress
Date: Aug 03, 2026
Research Description: The GEO my WP WordPress plugin before 4.5.5.3 does not perform any ownership or capability check on two of its logged-in AJAX actions, allowing users with subscriber-level access or above to modify or permanently delete other users' and posts' geolocation records by supplying arbitrary record IDs.
Affected versions: max 4.5.5.3.
Status: vulnerable