CVE-2026-13179: WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings · Cross-site Scripting
Affects WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & ListingsSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| flippercodeWP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict subscriber-level access where possible and monitor for suspicious activity related to the plugin. Avoid exposing the plugin to untrusted users. Follow vendor updates closely for an official fix.
Description
The WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shapes_values Parameter in all versions up to, and including, 4.9.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The fc-call-nonce nonce required by the endpoint is exposed to all frontend visitors who view a map page via window.wpgmp_local.nonce, enabling any authenticated subscriber to read the nonce and craft a valid request; additionally, the secondary _wpnonce check in the drawing handler can be bypassed by simply omitting the _wpnonce parameter from the request.
References
- wordfence.com/threat-intel/vulnerabilities/id/6c664543-1ca1-4ba8-a6c6-f32a560bc690?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/assets/js/maps.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/modules/drawing/views/manage.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/wp-google-map-plugin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/wp-google-map-plugin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/modules/shortcode/views/put-wpgmp.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/assets/js/maps.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/modules/drawing/views/manage.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/wp-google-map-plugin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/wp-google-map-plugin.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/modules/shortcode/views/put-wpgmp.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3690856%40wp-google-map-plugin&new=3690856%40wp-google-map-plugin (opens in a new tab)