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.
Published: 2026-08-03
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

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.

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

Remediation

No vendor fix or workaround currently provided.

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 yet.

History

Mon, 03 Aug 2026 18:30:00 +0000

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'}


Mon, 03 Aug 2026 07:45:00 +0000

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

Mon, 03 Aug 2026 06:45:00 +0000

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

Subscriptions

Geo My Wp Geo My Wp
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-03T17:31:14.812Z

Reserved: 2026-07-09T13:41:18.295Z

Link: CVE-2026-15260

cve-icon Vulnrichment

Updated: 2026-08-03T17:18:30.805Z

cve-icon NVD

Status : Received

Published: 2026-08-03T07:16:40.090

Modified: 2026-08-03T18:16:35.640

Link: CVE-2026-15260

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T10:45:05Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key