PatchSiren cyber security CVE debrief
CVE-2026-13179 flippercode CVE debrief
The WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator, Listing, Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the shapes_values parameter in all versions up to, and including, 4.9.8. This vulnerability allows 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.
- Vendor
- flippercode
- Product
- WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings
- CVSS
- MEDIUM 6.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Defenders responsible for WordPress installations using the WP Maps plugin, particularly those with users having subscriber-level access and above, should assess exposure and prioritize verification and potential remediation.
Why it matters
Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, particularly for users with subscriber-level access and above, and assess exposure to potential Stored Cross-Site Scripting attacks.
- Authenticated attackers with subscriber-level access can inject arbitrary web scripts
- Injected scripts execute when a user accesses an injected page
- Exposure requires verification due to limited information on affected versions and remediation
Technical summary
The WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator, Listing, Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the shapes_values parameter in all versions up to, and including, 4.9.8. This vulnerability allows 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.
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure, particularly for users with subscriber-level access and above.
Recommended defensive actions
- Verify the presence of this vulnerability in your WordPress installations
- Assess exposure, particularly for users with subscriber-level access and above
- Consider upgrading to a patched version of the WP Maps plugin
- Monitor for suspicious activity and implement additional security measures to prevent exploitation
- Perform a thorough review of the plugin's configuration and usage
- Implement a Web Application Firewall (WAF) to detect and prevent attacks
- Keep the plugin and WordPress core up-to-date
Evidence notes
The vulnerability is confirmed by the CVE Program and NVD records. The source references provided include links to the WordPress plugin repository and code files, indicating that the vulnerability has been identified and reported by security researchers.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-13179 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-13179
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-13179 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-13179
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/assets/js/maps.js
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/modules/drawing/views/manage.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/modules/shortcode/views/put-wpgmp.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.3/wp-google-map-plugin.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/assets/js/maps.js
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/modules/drawing/views/manage.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/modules/shortcode/views/put-wpgmp.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/wp-google-map-plugin/tags/4.9.5/wp-google-map-plugin.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.