CVE-2024-7380

Geo Controller <= 8.7.3 - Missing Authorization to Authenticated (Subscriber+) Menu Creation/Deletion

2024-09-04 21:33
Lucio Sá

Strategic Overview

Status
Patched in 8.7.4
Affected Plugin
Geo Controller
Affected Version
<= 8.7.3
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-7380
View all Geo Controller vulnerabilities

At a glance

CVE-2024-7380 is a medium-severity Missing Authorization vulnerability in the Geo Controller WordPress plugin, affecting versions <= 8.7.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.7.4; 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 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.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Geo Controller <= 8.7.3 takes an account at Subscriber level or above. 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.4: builds <= 8.7.3 are affected, anything from 8.7.4 onward is not.

Remediation

Update to version 8.7.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Geo Controller 8.7.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-7380https://www.wordfence.com/threat-intel/vulnerabilities/id/280e1b4d-08be-4e77-abcb-5f9079111595https://nvd.nist.gov/vuln/detail/CVE-2024-7380

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C