CVE-2026-15260

Geo My WP < 4.5.5.3 - Subscriber+ Arbitrary Geolocation Record Modification and Deletion via IDOR

Published Aug 3, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The GEO my WP WordPress plugin allows users with subscriber-level access or higher to invoke two logged‑in AJAX actions that update or permanently delete geolocation records, without verifying that the user owns the target record. This insecure direct object reference (IDOR) permits the attacker to change or remove any user's or post's geolocation data, compromising data integrity and potentially exposing sensitive location information.

Affected Systems

WordPress sites that use the GEO my WP plugin in a version earlier than 4.5.5.3. Site administrators should verify the plugin version and be aware that all logged‑in users with subscriber or higher capability can trigger the vulnerable AJAX endpoints.

Risk and Exploitability

The vulnerability is scored a moderate severity of 4.3 on the CVSS scale, and has an EPSS of less than 1%, indicating a low likelihood of widespread exploitation. Still, an authenticated attacker with subscriber or higher capabilities can send a crafted request to the vulnerable AJAX endpoint, using an arbitrary record ID to update or permanently delete any user or post geolocation data. Because no ownership checks are performed, the attack requires only legitimate credentials, making it relatively easy to execute. Although not listed in the CISA KEV catalog, the potential to tamper with or erase location data poses significant integrity and confidentiality risks for affected sites.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the GEO my WP plugin to version 4.5.5.3 or later, which implements proper ownership checks on the affected AJAX actions.
  • If an upgrade is not immediately possible, remove or disable the vulnerable AJAX endpoints via custom code or plugin settings, ensuring that subscriber accounts cannot trigger them.
  • Limit the capabilities of subscriber roles within WordPress so that they do not have access to the GEO my WP configuration and cannot manage geolocation records.

Generated by OpenCVE AI on August 4, 2026 at 10:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-639
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Geo My Wp
Geo My Wp geo My Wp
Wordpress
Wordpress wordpress
Vendors & Products Geo My Wp
Geo My Wp geo My Wp
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description 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.
Title Geo My WP < 4.5.5.3 - Subscriber+ Arbitrary Geolocation Record Modification and Deletion via IDOR
References
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 3, 2026, 5:31 PM
Reserved
Jul 9, 2026, 1:41 PM
Status
Deferred
Published
Aug 3, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM