CVE-2025-11166 MEDIUM

CVE-2025-11166: WP Go Maps (formerly WP Google Maps) <= 9.0.46 - Cross-Site Request Forgery to Plugin Settings Update

Vendor Wpgmaps
Product WP Go Maps (formerly WP Google Maps)
Weakness CWE-352 · CSRF
Published October 9, 2025
Last update April 8, 2026

CVSS base score

5.4/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

What the vulnerability does

01Description

The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to, and including, 9.0.46. This is due to the plugin exposing state-changing REST actions through an AJAX bridge without proper CSRF token validation, and having destructive logic reachable via GET requests with no permission_callback. This makes it possible for unauthenticated attackers to force logged-in administrators to create, update, or delete markers and geometry features via CSRF attacks, and allows anonymous users to trigger mass deletion of markers via unsafe GET requests.

Explanation of Vulnerability in Simple Terms

02Summary

WP Go Maps versions 9.0.46 and earlier contain a cross-site request forgery (CSRF) vulnerability. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. This could allow modification or deletion of map data and settings. The vulnerability requires user interaction—the admin must visit the attacker's page while logged into WordPress.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into modifying or deleting maps and map settings via a malicious webpage.

Potential impact on your site

04Site Impact

Maps and their configuration could be altered or deleted without your consent if an admin visits a malicious link.

Conditions required to exploit

05Prerequisites

Admin must visit attacker-controlled webpage while logged into WordPress.

Key dates

06Disclosure timeline

October 9, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE