Geo My WP <= 4.5.5.2 — Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Geolocation Record Modification and Deletion
CVE-2026-15260Published · Updated Action summary
Affected: ≤4.5.5.2Update to 4.5.5.3 or newer
All remediation steps- Severity
- Medium4.3
- CVSS
- 4.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- Unknown
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
GEO my WP geo-my-wp
- Affected≤ 4.5.5.2
- Patched in4.5.5.3
Update to 4.5.5.3 or newer.
You are affected if you run ≤ 4.5.5.2. Version 4.5.5.3 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under GEO my WP.
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 4.5.5.3, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch GEO my WP to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Yaswanth Reddy Sunkara.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in GEO my WP
All 15| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Missing Authorization ≤4.5.5.5Update to 4.5.5.7 | CVE-2026-114193 | |
| High8.1 | Unauthenticated PHP Object Injection ≤4.5.5.3Update to 4.5.5.4 | CVE-2026-61992 | |
| High7.5 | Unauthenticated Local File Inclusion ≤4.5.5.3Update to 4.5.5.4 | CVE-2026-85200 | |
| High7.5 | Unauthenticated SQL Injection ≤4.5.5Update to 4.5.5.1 | CVE-2026-52715 | |
| High7.5 | Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters ≤4.5.5Update to 4.5.5.1 | CVE-2026-9757 |
- Medium5.3Missing Authorization
≤4.5.5.5Update to 4.5.5.7
- High8.1Unauthenticated PHP Object Injection
≤4.5.5.3Update to 4.5.5.4
- High7.5Unauthenticated Local File Inclusion
≤4.5.5.3Update to 4.5.5.4
- High7.5Unauthenticated SQL Injection
≤4.5.5Update to 4.5.5.1
- High7.5Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters
≤4.5.5Update to 4.5.5.1
Timeline
CVE published
Severity medium, CVSS 4.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.