WordPress security changelog
MEDIUM CVE-2025-11703 Deferred

WP Go Maps (formerly WP Google Maps): A security weakness

WP Go Maps (formerly WP Google Maps) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
WP Go Maps (formerly WP Google Maps)
Plugin slug
wp-go-maps-formerly-wp-google-maps
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 18, 2025
Weakness
CWE-349 — Acceptance of Extraneous Untrusted Data With Trusted Data

This CVE was published Oct 18, 2025 and is one of 3 known issues for this plugin.

Update, patch or deactivate.

Update WP Go Maps (formerly WP Google Maps) to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Cache Poisoning in all versions up to, and including, 9.0.48. This is due to the plugin not serving cached data from server-side responses and instead relying on user-input. This makes it possible for unauthenticated attackers to poison the cache location for location search results.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary and upstream sources