VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

WP Go Maps (formerly WP Google Maps) <= 9.0.48 — Unauthenticated Cache Poisoning

CVE-2025-11703Published · Updated

Action summary

Affected: ≤9.0.48Update to 9.0.49 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator wp-google-maps

  1. Affected≤ 9.0.48
  2. Patched in9.0.49

Update to 9.0.49 or newer.

You are affected if you run ≤ 9.0.48. Version 9.0.49 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 9.0.49, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Dmitrii Ignatyev.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator

All 29
More vulnerabilities in WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator
SeverityVulnerabilityCVEPublished
High7.5Unauthenticated Denial of Service
≤10.1.08Update to 10.1.09
CVE-2026-84780
High7.5Unauthenticated SQL Injection
<10.1.04Update to 10.1.04
CVE-2026-15381
Medium5.3Missing Authorization
≤10.1.05Update to 10.1.06
CVE-2026-25466
Medium5.3Unauthenticated Arbitrary Record Creation
≤10.1.01Update to 10.1.02
CVE-2026-12238
Medium5.3Unauthenticated Sensitive Information Disclosure via Datatables AJAX Fallback
≤10.0.09Update to 10.0.10
CVE-2026-8385

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?