HomeWordPress vulnerabilitiesGEO my WP
GEO my WP vulnerabilities
GEO my WP has 12 known vulnerabilities in this database. The most recent published record is dated 12 Sep 2026.
- Known vulnerabilities
- 12
- Active installs
- 3,000+
- Latest version
- 4.5.5.4
- Last updated
- 10 Sep 2026
- Most recent
- 12 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-85200 | High 7.5 | Up to 4.5.5.3 | Fixed in a later version (latest 4.5.5.4) | 12 Sep 2026 |
| Broken access control CVE-2026-15260 | Medium 4.3 | Before 4.5.5.3 | Fixed in 4.5.5.3 | 3 Aug 2026 |
| SQL injection CVE-2026-15300 | Critical 9.1 | Up to 4.5.4 | Fixed in a later version (latest 4.5.5.4) | 10 Jul 2026 |
| SQL injection CVE-2026-52715 | Critical 9.3 | Not yet published | Check for an update | 16 Jun 2026 |
| SQL injection CVE-2026-9757 | High 7.5 | Up to 4.5.5 | Fixed in a later version (latest 4.5.5.4) | 30 May 2026 |
| Broken access control CVE-2024-54326 | Medium 6.5 | Up to 4.5.0.4 | Fixed in a later version (latest 4.5.5.4) | 13 Dec 2024 |
| Security weakness CVE-2024-9422 | Medium 6.6 | Before 3.1 | Fixed in 3.1 | 22 Nov 2024 |
| Cross-site scripting (XSS) CVE-2024-47327 | High 7.1 | Up to 4.5.0.3 | Fixed in a later version (latest 4.5.5.4) | 6 Oct 2024 |
| Remote code execution CVE-2024-6330 | Critical 9.8 | Before 4.5.0.2 | Fixed in 4.5.0.2 | 19 Aug 2024 |
| Cross-site request forgery (CSRF) CVE-2024-32097 | Medium 5.4 | Up to 4.1 | Fixed in a later version (latest 4.5.5.4) | 15 Apr 2024 |
| SQL injection CVE-2023-52134 | High 7.6 | Up to 4.0.2 | Fixed in a later version (latest 4.5.5.4) | 31 Dec 2023 |
| Cross-site scripting (XSS) CVE-2023-5467 | Medium 6.4 | Up to 4.0 | Fixed in a later version (latest 4.5.5.4) | 10 Oct 2023 |
Read the published descriptions
- CVE-2026-85200, 12 Sep 2026
- The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_ajax_info_window_loader function. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. In environments where PEAR is installed with register_argc_argv enabled, this file inclusion can be leveraged to write and execute arbitrary PHP code, achieving full remote code execution. CVE record
- CVE-2026-15260, 3 Aug 2026
- 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. CVE record
- CVE-2026-15300, 10 Jul 2026
- 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. CVE record
- CVE-2026-52715, 16 Jun 2026
- Unauthenticated SQL Injection in GEO my WordPress <= 4.5.5 versions. CVE record
- CVE-2026-9757, 30 May 2026
- 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. CVE record
- CVE-2024-54326, 13 Dec 2024
- 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. CVE record
- CVE-2024-9422, 22 Nov 2024
- 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. CVE record
- CVE-2024-47327, 6 Oct 2024
- 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. CVE record
- CVE-2024-6330, 19 Aug 2024
- 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. CVE record
- CVE-2024-32097, 15 Apr 2024
- Cross-Site Request Forgery (CSRF) vulnerability in Eyal Fitoussi GEO my WordPress.This issue affects GEO my WordPress: from n/a through 4.1. CVE record
- CVE-2023-52134, 31 Dec 2023
- 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. CVE record
- CVE-2023-5467, 10 Oct 2023
- 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. CVE record
What to do if you run GEO my WP
If you run GEO my WP, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GEO my WP vulnerabilities
Free. We email you when a new vulnerability is published for GEO my WP, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.