CVE-2025-11703: CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data in wpgmaps WP Go Maps (formerly WP Google Maps)
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.
AI Analysis
Technical Summary
CVE-2025-11703 is a vulnerability classified under CWE-349, which involves the acceptance of extraneous untrusted data alongside trusted data. The WP Go Maps plugin for WordPress, widely used to embed and manage maps and location searches, suffers from a cache poisoning flaw in all versions up to and including 9.0.48. The root cause is the plugin's design choice to serve cached location search results based on user input rather than validating or generating cache entries solely from trusted server-side data. This architectural weakness allows an unauthenticated attacker to inject malicious or manipulated data into the cache storage. When subsequent users request location data, they may receive poisoned or incorrect results, undermining the integrity of the information presented. The vulnerability does not expose confidential data nor does it impact system availability, but it compromises data integrity by allowing tampered location information to be served. The CVSS v3.1 base score is 5.3 (medium severity), reflecting the ease of remote exploitation without authentication or user interaction, but limited impact scope. No patches or known exploits are currently available, though the vulnerability has been publicly disclosed. This issue is particularly relevant for websites that rely heavily on accurate location data for business operations or user navigation, as poisoned caches could misdirect users or damage organizational reputation.
Potential Impact
For European organizations, the primary impact of CVE-2025-11703 lies in the integrity of location-based data served via WordPress sites using the WP Go Maps plugin. Poisoned cache entries could lead to incorrect or misleading location search results, potentially disrupting customer experience, logistics, or service delivery. While confidentiality and availability remain unaffected, the integrity compromise could erode trust in digital services, especially for businesses relying on accurate geographic information such as retail, travel, real estate, and local services. Organizations in sectors with regulatory requirements for data accuracy and integrity may face compliance risks if manipulated data leads to erroneous decisions or customer harm. Additionally, attackers could leverage this vulnerability to conduct targeted misinformation campaigns or reputational attacks by injecting false location data. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing risk exposure. However, the absence of known exploits in the wild suggests limited immediate threat but underscores the need for proactive mitigation.
Mitigation Recommendations
To mitigate CVE-2025-11703 effectively, European organizations should first monitor for and apply any official patches released by the WP Go Maps plugin developers promptly. Until a patch is available, administrators should consider disabling the plugin or its location search caching features if feasible. Implementing server-side validation and sanitization of all inputs used to generate cache entries is critical to prevent acceptance of untrusted data. Organizations can also deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to manipulate cache parameters. Regularly auditing cache contents for anomalies or unexpected data can help detect poisoning attempts early. Additionally, restricting access to cache storage locations and employing integrity verification mechanisms, such as cryptographic hashes or signatures for cached data, can reduce risk. Educating site administrators about the risks and encouraging minimal use of caching for dynamic location data until the vulnerability is resolved will further reduce exposure.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain
CVE-2025-11703: CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data in wpgmaps WP Go Maps (formerly WP Google Maps)
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-11703 is a vulnerability classified under CWE-349, which involves the acceptance of extraneous untrusted data alongside trusted data. The WP Go Maps plugin for WordPress, widely used to embed and manage maps and location searches, suffers from a cache poisoning flaw in all versions up to and including 9.0.48. The root cause is the plugin's design choice to serve cached location search results based on user input rather than validating or generating cache entries solely from trusted server-side data. This architectural weakness allows an unauthenticated attacker to inject malicious or manipulated data into the cache storage. When subsequent users request location data, they may receive poisoned or incorrect results, undermining the integrity of the information presented. The vulnerability does not expose confidential data nor does it impact system availability, but it compromises data integrity by allowing tampered location information to be served. The CVSS v3.1 base score is 5.3 (medium severity), reflecting the ease of remote exploitation without authentication or user interaction, but limited impact scope. No patches or known exploits are currently available, though the vulnerability has been publicly disclosed. This issue is particularly relevant for websites that rely heavily on accurate location data for business operations or user navigation, as poisoned caches could misdirect users or damage organizational reputation.
Potential Impact
For European organizations, the primary impact of CVE-2025-11703 lies in the integrity of location-based data served via WordPress sites using the WP Go Maps plugin. Poisoned cache entries could lead to incorrect or misleading location search results, potentially disrupting customer experience, logistics, or service delivery. While confidentiality and availability remain unaffected, the integrity compromise could erode trust in digital services, especially for businesses relying on accurate geographic information such as retail, travel, real estate, and local services. Organizations in sectors with regulatory requirements for data accuracy and integrity may face compliance risks if manipulated data leads to erroneous decisions or customer harm. Additionally, attackers could leverage this vulnerability to conduct targeted misinformation campaigns or reputational attacks by injecting false location data. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing risk exposure. However, the absence of known exploits in the wild suggests limited immediate threat but underscores the need for proactive mitigation.
Mitigation Recommendations
To mitigate CVE-2025-11703 effectively, European organizations should first monitor for and apply any official patches released by the WP Go Maps plugin developers promptly. Until a patch is available, administrators should consider disabling the plugin or its location search caching features if feasible. Implementing server-side validation and sanitization of all inputs used to generate cache entries is critical to prevent acceptance of untrusted data. Organizations can also deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to manipulate cache parameters. Regularly auditing cache contents for anomalies or unexpected data can help detect poisoning attempts early. Additionally, restricting access to cache storage locations and employing integrity verification mechanisms, such as cryptographic hashes or signatures for cached data, can reduce risk. Educating site administrators about the risks and encouraging minimal use of caching for dynamic location data until the vulnerability is resolved will further reduce exposure.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-13T18:54:06.234Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68f33944197c8629076f80e5
Added to database: 10/18/2025, 6:52:52 AM
Last enriched: 10/25/2025, 9:56:17 AM
Last updated: 12/4/2025, 2:28:39 PM
Views: 98
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14005: Cross Site Scripting in dayrui XunRuiCMS
MediumCVE-2025-14004: Server-Side Request Forgery in dayrui XunRuiCMS
MediumCVE-2025-11222: na in LINE Corporation Central Dogma
Medium5 Threats That Reshaped Web Security This Year [2025]
MediumPersonal Information Compromised in Freedom Mobile Data Breach
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.