CVE-2025-13364
Received Received - Intake
Stored XSS in WP Maps Plugin via 'put_wpg' Shortcode

Publication date: 2026-04-16

Last updated on: 2026-04-16

Assigner: Wordfence

Description
The WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'put_wpgm' shortcode in all versions up to, and including, 4.8.7. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-16
Last Modified
2026-04-16
Generated
2026-05-07
AI Q&A
2026-04-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wp_maps_store_locator wp_maps_store_locator to 4.8.7 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The WP Maps – Store Locator, Google Maps, OpenStreetMap, Mapbox, Listing, Directory & Filters plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 4.8.7.

This vulnerability arises because the plugin does not properly sanitize or escape user-supplied input in the 'put_wpgm' shortcode attributes.

As a result, authenticated users with contributor level access or higher can inject malicious scripts into pages, which then execute whenever any user views those pages.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows authenticated attackers with contributor level access and above to inject arbitrary web scripts via stored cross-site scripting (XSS). This can lead to unauthorized access to user data or session hijacking, potentially compromising confidentiality and integrity of data.

Such security weaknesses can impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and attacks.

However, the provided information does not explicitly detail the direct effects on compliance or specific regulatory implications.


How can this vulnerability impact me? :

This vulnerability can allow attackers with contributor or higher access to inject arbitrary web scripts into your website's pages.

These malicious scripts can execute in the browsers of users who visit the infected pages, potentially leading to theft of user credentials, session hijacking, or other malicious actions.

Because the vulnerability requires authenticated access, it mainly impacts sites where contributors or similar roles are allowed to add content.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves Stored Cross-Site Scripting via the 'put_wpgm' shortcode in the WP Maps plugin for WordPress. Detection would involve scanning WordPress pages and posts for injected scripts within the 'put_wpgm' shortcode attributes.

Since the vulnerability requires contributor level access or above to exploit, monitoring user inputs and shortcode usage in WordPress content is essential.

Specific commands are not provided in the available resources, but typical detection methods could include searching the WordPress database or exported content for suspicious script tags or JavaScript within 'put_wpgm' shortcode attributes.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include updating the WP Maps – Store Locator plugin to a version later than 4.8.7 where the vulnerability is fixed.

If an update is not immediately possible, restrict contributor level access or higher to trusted users only, as the vulnerability requires authenticated users with such privileges.

Additionally, consider implementing Web Application Firewall (WAF) rules to block malicious scripts and monitor for unusual shortcode usage.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart