WP Maps <= 4.9.4 - Authenticated (Admin+) Stored Cross-Site Scripting via 'location_messages' Parameter
Strategic Overview
- Status
- Patched in 4.9.5
- Affected Version
<= 4.9.4- CVSS
- 4.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-9594
At a glance
CVE-2026-9594 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Maps WordPress plugin, affecting versions <= 4.9.4. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 4.9.5; sites on affected versions should update now. Disclosed June 2026, reported by Yousef Alraddadi.
Vulnerability Overview
The WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'location_messages' parameter in all versions up to, and including, 4.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to hold the custom wpgmp_manage_location capability, which is granted to administrators by default but can be assigned to lower-privileged roles via the plugin's Permissions screen.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
WP Maps <= 4.9.4 carries this weakness at location_messages, and reaching it takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Maps the fix is 4.9.5: builds <= 4.9.4 are affected, anything from 4.9.5 onward is not.
Remediation
Update to version 4.9.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Maps 4.9.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters
- 8.8CVE-2025-12062: WP Maps <= 4.8.6 Limited Local File Inclusion
CVE-2025-12062 - 8.8CVE-2024-2386: WordPress for Google Maps – WP MAPS SQL Injection
CVE-2024-2386 - 8.8WP Google Map Plugin <= 4.0.9 CSRF to PHP Object Injection
- 8.8CVE-2015-9309: WP Google Map Plugin < 2.3.10 CSRF
CVE-2015-9309 - 8.8CVE-2015-9307: WP Google Map Plugin < 2.3.10 CSRF
CVE-2015-9307 - 8.8CVE-2015-9308: WP Google Map Plugin < 2.3.10 CSRF
CVE-2015-9308 - 7.5CVE-2026-6381: WP Maps LFI
CVE-2026-6381 - 7.5CVE-2026-39492: WP Maps SQL Injection
CVE-2026-39492
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C