CVE-2026-15260

Geo My WP <= 4.5.5.2 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Geolocation Record Modification and Deletion

2026-07-24 00:00
Yaswanth Reddy Sunkara

Strategic Overview

Status
Patched in 4.5.5.3
Affected Plugin
GEO my WP
Affected Version
<= 4.5.5.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-15260
View all GEO my WP vulnerabilities

At a glance

CVE-2026-15260 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the GEO my WP WordPress plugin, affecting versions <= 4.5.5.2. 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 4.5.5.3; sites on affected versions should update now. Disclosed July 2026, reported by Yaswanth Reddy Sunkara.

Vulnerability Overview

The Geo My WP plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 4.5.5.2. This is due to missing ownership verification against the stored record when processing an existing location ID, allowing the submitted object_type and object_id to bypass the capability check instead of the values fetched from the database. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify or delete arbitrary geolocation records belonging to other users by supplying a foreign location record ID.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in GEO my WP <= 4.5.5.2 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For GEO my WP the fix is 4.5.5.3: builds <= 4.5.5.2 are affected, anything from 4.5.5.3 onward is not.

Remediation

Update to version 4.5.5.3, 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 my WP 4.5.5.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15260https://www.wordfence.com/threat-intel/vulnerabilities/id/f03dd6f4-44ca-4afe-b3fa-8770fca8a067https://nvd.nist.gov/vuln/detail/CVE-2026-15260

Related records

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