Geo Controller <= 8.6.9 - Missing Authorization to Unauthenticated Shortcode Execution
Strategic Overview
- Status
- Patched in 8.7.0
- Affected Plugin
- Geo Controller
- Affected Version
<= 8.6.9- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-7381
At a glance
CVE-2024-7381 is a medium-severity Missing Authorization vulnerability in the Geo Controller WordPress plugin, affecting versions <= 8.6.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.7.0; sites on affected versions should update now. Disclosed September 2024, reported by Lucio Sá.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Geo Controller <= 8.6.9 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Geo Controller the fix is 8.7.0: builds <= 8.6.9 are affected, anything from 8.7.0 onward is not.
Remediation
Update to version 8.7.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Geo Controller 8.7.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Geo Controller
- 8.8CVE-2024-3591: Geo Controller <= 8.6.4 PHP Object Injection
CVE-2024-3591 - 8.1CVE-2026-78286: Geo Controller <= 8.9.8 PHP Object Injection
CVE-2026-78286 - 6.4CVE-2024-30451: Geo Controller <= 8.6.4 Stored Cross-Site Scripting
CVE-2024-30451 - 6.4CVE-2023-51513: Geo Controller <= 8.5.2 Stored Cross-Site Scripting
CVE-2023-51513 - 6.1WordPress Geolocation Plugin – CF Geo Plugin <= 7.13.11 Reflected XSS
- 5.3CVE-2025-62109: Geo Controller <= 8.9.5 Information Exposure
CVE-2025-62109
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C