Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11166: CWE-352 Cross-Site Request Forgery (CSRF) in wpgmaps WP Go Maps (formerly WP Google Maps)

0
Medium
VulnerabilityCVE-2025-11166cvecve-2025-11166cwe-352
Published: Thu Oct 09 2025 (10/09/2025, 01:48:48 UTC)
Source: CVE Database V5
Vendor/Project: wpgmaps
Product: WP Go Maps (formerly WP Google Maps)

Description

CVE-2025-11166 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability affecting all versions of the WP Go Maps WordPress plugin up to 9. 0. 46. The flaw arises from improper CSRF token validation on state-changing REST actions exposed via an AJAX bridge, combined with destructive logic accessible through unauthenticated GET requests lacking permission checks. This allows unauthenticated attackers to force logged-in administrators to create, update, or delete map markers and geometry features, and enables anonymous users to trigger mass deletion of markers. Exploitation requires user interaction for administrator-targeted attacks but not for anonymous mass deletion via GET requests. No known exploits are reported in the wild yet. The vulnerability impacts the integrity and availability of map data on affected WordPress sites. European organizations using WP Go Maps, especially those with public-facing WordPress sites relying on this plugin, are at risk. Mitigation involves updating the plugin once a patch is released, restricting access to administrative interfaces, and implementing web application firewall (WAF) rules to block suspicious CSRF attempts and unauthorized GET requests.

AI-Powered Analysis

AILast updated: 10/16/2025, 08:52:13 UTC

Technical Analysis

CVE-2025-11166 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WP Go Maps WordPress plugin (formerly WP Google Maps) affecting all versions up to 9.0.46. The vulnerability stems from the plugin exposing state-changing REST API actions through an AJAX bridge without proper CSRF token validation, violating secure design principles. Additionally, destructive operations are accessible via HTTP GET requests that lack a permission_callback, meaning no authentication or authorization checks are enforced for these actions. This combination allows an attacker to craft malicious web requests that, when visited by a logged-in administrator, can force unintended creation, modification, or deletion of map markers and geometry features. More critically, anonymous users can exploit unsafe GET endpoints to trigger mass deletion of markers without any authentication or user interaction. The CVSS 3.1 base score is 5.4 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, but requiring user interaction for some attack vectors. The vulnerability impacts the integrity and availability of map data managed by the plugin, potentially disrupting website functionality and user experience. No public exploits have been reported yet, but the vulnerability is publicly disclosed and should be considered exploitable. The root cause is insufficient validation of CSRF tokens and missing permission checks on REST endpoints, which are fundamental security oversights in WordPress plugin development. Organizations using this plugin should monitor for updates and apply patches promptly once available.

Potential Impact

For European organizations, the vulnerability poses a risk to the integrity and availability of map-related data on WordPress sites using WP Go Maps. Attackers can manipulate or delete critical geographic markers, potentially disrupting services that rely on accurate mapping information, such as logistics, retail location services, tourism, and public information portals. The ability for unauthenticated users to cause mass deletion of markers via GET requests increases the risk of denial-of-service conditions on mapping features. This can degrade user trust and operational continuity. Since WordPress is widely used across Europe, and WP Go Maps is a popular plugin for embedding maps, the threat surface is significant. Organizations with high-value or public-facing WordPress sites are particularly vulnerable, especially if administrators are targeted via CSRF attacks. The disruption could affect customer engagement, internal operations, and compliance with data integrity requirements. Given the medium severity, the threat is moderate but should not be underestimated, especially in sectors where mapping data is critical.

Mitigation Recommendations

1. Monitor the WP Go Maps plugin repository and vendor announcements closely for the release of a security patch addressing CVE-2025-11166 and apply it immediately upon availability. 2. Until a patch is available, restrict access to WordPress administrative interfaces to trusted IP addresses or VPNs to reduce exposure to CSRF attacks targeting logged-in administrators. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious CSRF attempts and unauthorized GET requests targeting the plugin’s REST endpoints. 4. Educate WordPress administrators about the risks of CSRF and encourage them to avoid clicking on untrusted links while logged into the admin panel. 5. Review and harden WordPress REST API permissions and consider disabling or limiting the WP Go Maps REST endpoints if feasible. 6. Regularly back up WordPress site data, including map markers and geometry features, to enable rapid restoration in case of data manipulation or deletion. 7. Conduct security audits of installed plugins to identify other potential vulnerabilities and ensure all plugins are kept up to date. 8. Consider deploying Content Security Policy (CSP) headers to reduce the risk of malicious cross-site requests.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-29T16:49:57.375Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e71ce832de7eb26af6c05d

Added to database: 10/9/2025, 2:24:40 AM

Last enriched: 10/16/2025, 8:52:13 AM

Last updated: 11/22/2025, 8:13:32 PM

Views: 83

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats