HomeWordPress vulnerabilitiesGeo Controller
Geo Controller vulnerabilities
Geo Controller has 3 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2024.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 9.0.1
- Last updated
- 11 Sep 2026
- Most recent
- 5 Sep 2024
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 |
|---|---|---|---|---|
| Broken access control CVE-2024-7381 | Medium 5.3 | Up to 8.6.9 | Fixed in a later version (latest 9.0.1) | 5 Sep 2024 |
| Broken access control CVE-2024-7380 | Medium 4.3 | Up to 8.6.9 | Fixed in a later version (latest 9.0.1) | 5 Sep 2024 |
| PHP object injection CVE-2024-3591 | Medium 6.5 | Before 8.6.5 | Fixed in 8.6.5 | 1 May 2024 |
Read the published descriptions
- CVE-2024-7381, 5 Sep 2024
- The Geo Controller plugin for WordPress is vulnerable to unauthorized shortcode execution due to missing authorization and capability checks on the ajax__shortcode_cache function in all versions up to, and including, 8.6.9. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes available on the target site. CVE record
- CVE-2024-7380, 5 Sep 2024
- The Geo Controller plugin for WordPress is vulnerable to unauthorized menu creation/deletion due to missing capability checks on the ajax__geolocate_menu and ajax__geolocate_remove_menu functions in all versions up to, and including, 8.7.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create or delete WordPress menus. CVE record
- CVE-2024-3591, 1 May 2024
- The Geo Controller WordPress plugin before 8.6.5 unserializes user input via some of its AJAX actions and REST API routes, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog. CVE record
What to do if you run Geo Controller
If you run Geo Controller, 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 Controller vulnerabilities
Free. We email you when a new vulnerability is published for Geo Controller, 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.