Vulnerability · CVE-2025-11166
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.
Published Oct 9, 2025 · catalog updated Apr 8, 2026 · WP Go Maps (formerly WP Google Maps)
Check this week
CVE-2025-11166 is not in CISA KEV. FIRST estimates a 19.00% chance of exploitation in the next 30 days. Check whether you run WP Go Maps (formerly WP Google Maps).
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.4
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 19.00%
- Remediation
- Vendor / distro source
- Affected products
- vendor wpgmaps WP Go Maps (formerly WP Google Maps) 0 ≤9.0.46
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 u
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor wpgmaps WP Go Maps (formerly WP Google Maps) 0 ≤9.0.460 ≤9.0.46
How to fix CVE-2025-11166
Recommended remediation
A vendor or distribution source is linked. Check that advisory for patch availability; this catalog does not invent fix status.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-11166 is not in CISA KEV. FIRST estimates a 19.00% chance of exploitation in the next 30 days. Check whether you run WP Go Maps (formerly WP Google Maps).
Which versions are affected?
Compare what you have installed with wpgmaps WP Go Maps (formerly WP Google Maps) 0 ≤9.0.46 0 ≤9.0.46. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 19.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 9, 2025 · EUVD
Detected
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 unaut
Apr 8, 2026 · EUVD
Updated
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 unaut
Sources
- EUVDVulnerability recordEUVD-2025-33264
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 validatio
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Apr 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.