Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-15260

CVE-2026-15260 - Before 4 Plugin

CVE-2026-15260

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.

CVE-2026-15260

UNKNOWN CVSS 0.0 Published 2026-08-03 Updated 2026-08-03
AI Risk Low (5/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band UNKNOWN
CVSS Vector Unspecified
Affected Components 2
Reference Links 1
AI Risk Engine Low (5/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-03 CVE published and first recorded in the threat feed.
  2. 2026-08-03 Record updated with latest vulnerability metadata.
  3. 2026-08-03 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 20 hours ago

AI enriched 20 hours ago (2026-08-03 22:58 UTC)

Technical Summary

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.

Potential Impact

Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 5/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Before 4 PLUGIN · before-4 Affected: < 4.5.5.3 Fixed in: 4.5.5.3
Geo My Wp PLUGIN · geo-my-wp Affected: < 4.5.5.3 Fixed in: 4.5.5.3
Scroll to top