Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/obtain subscriber account
-
DeliveryRead exposed fc-call-nonce from window.wpgmp_local.nonce
-
ExploitSubmit crafted shapes_values payload omitting _wpnonce
-
ExecutionMalicious script stored in map data
-
PersistAdmin/visitor views map page
-
ImpactScript executes in victim browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with at least subscriber-level access on a site running WP Maps (wp-google-map-plugin) <=4.9.8; practically this means the site allows open user registration or the attacker otherwise holds low-privilege credentials. The normal fc-call-nonce barrier is not a meaningful limit because it is exposed to all frontend visitors via window.wpgmp_local.nonce on any map page, and the drawing handler's secondary _wpnonce check can be bypassed by omitting the parameter. Realization of impact requires a victim (e.g., an administrator or site visitor) to subsequently view the page containing the injected shapes_values payload, so payload execution is deferred until page view rather than immediate. |
| Impact | This is a genuine but moderate-severity issue, best characterized as a real-but-low-priority stored XSS. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) is internally consistent with the description: network-reachable, low complexity, requires low privileges (subscriber), scope-changed because injected script executes in other users' browser context, with limited confidentiality/integrity impact and no availability impact. No EPSS score, KEV listing, or public POC was provided in the input, so exploitation status is 'no public exploit identified at time of analysis.' The notable risk amplifier called out in the description is that the required fc-call-nonce is exposed to ALL frontend visitors via window.wpgmp_local.nonce, and the secondary _wpnonce check in the drawing handler can be bypassed by omitting the parameter entirely - this means the nonce protection provides effectively no barrier, so any subscriber-level account can reliably craft a valid request. That lowers real attack complexity relative to typical nonce-gated WordPress endpoints, though PR:L still correctly gates on having an authenticated subscriber account. Net: prioritize patching on sites that allow open/self-registration (where subscriber accounts are trivially obtained), but this is not a high-CVSS-but-fake issue nor an internet-wide unauthenticated RCE. |
| Exploit ScenarioDerived | On a WordPress site running WP Maps <=4.9.8 that permits user self-registration, an attacker registers a subscriber account, reads the exposed fc-call-nonce from window.wpgmp_local.nonce on any public map page (and/or simply omits _wpnonce to bypass the drawing handler's secondary check), and submits a crafted request injecting a malicious script into the shapes_values parameter. The payload is stored and later executes in the browser of any user (including administrators) who views the affected map page, enabling session/cookie theft or actions in the victim's context. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Stored cross-site scripting in the WordPress plugin WP Maps - Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings (wp-google-map-plugin) in all versions up to and including 4.9.8 allows authenticated attackers holding only subscriber-level access to inject arbitrary JavaScript through the shapes_values parameter, which is insufficiently sanitized on input and unescaped on output. The nominal fc-call-nonce protection is ineffective because that nonce is exposed to every frontend visitor via window.wpgmp_local.nonce on map pages, and the drawing handler's secondary _wpnonce check can be bypassed simply by omitting the _wpnonce parameter from the request. Execution is deferred: the injected script fires when a victim (for example an administrator or any site visitor) later views the page containing the stored shape, and no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
RemediationAI
Upgrade the WP Maps plugin past the affected range as soon as a patched release is published; the Trac changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3690856%40wp-google-map-plugin&new=3690856%40wp-google-map-plugin (revision 3690856) appears to contain the upstream fix, but a tagged, independently verified patched version was not confirmed in the available data, so treat the fix as upstream-commit-level and verify the installed version against the plugin's release notes rather than assuming 4.9.8 is safe. Because the primary weakness is the combination of an exposed nonce and a bypassable _wpnonce check, the most effective interim controls are to eliminate the low-privilege foothold and the exposed surface: disable open user registration (Settings → General) so attackers cannot self-provision a subscriber account - the trade-off is that legitimate self-service signups stop working; audit and remove unnecessary subscriber-level accounts; and if the drawing/shape feature is not needed, disable it or remove the plugin's drawing module so the shapes_values handler is unreachable, accepting the loss of map-shape annotation functionality. Site operators can also place a WAF or reverse-proxy rule in front of the site to reject requests whose shape payloads contain script markup, but such signatures are trivially bypassed with encoding or mixed-case variants, so this is a supplement rather than a substitute for patching. Finally, because the handler's nonce verification can be skipped by omitting _wpnonce, do not rely on nonces alone: ensure capability checks on the drawing endpoint are enforced server-side, and continue monitoring the Wordfence advisory page for an official patched version and CVE-specific guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic CWE-79 improper-neutralization issue in a WordPress plugin, where user-controlled data from an AJAX-style request reaches the browser without sanitization or context-aware output escaping. The vulnerable path is the plugin's map-drawing feature: chart shape data submitted as the shapes_values parameter is persisted and later rendered by the plugin's PHP views without escaping. The CPE string identifies the vendor as flippercode and the product as the WP Maps plugin, with a wildcard version, indicating that no version range is constrained in the CPE - consistent with the advisory statement that all releases through 4.9.8 are affected. The reference code paths illuminate the mechanism: wp-google-map-plugin.php lines 605 and 619 relate to nonce creation and handling, modules/shortcode/views/put-wpgmp.php line 1263 is where the frontend window.wpgmp_local object (including the nonce) is exposed to all visitors, assets/js/maps.js line 8477 is frontend JavaScript that consumes that localized nonce, and modules/drawing/views/manage.php line 32 is the drawing management view where shape output is emitted. Because the attacker-supplied markup executes in the origin of the WordPress site rather than a sandboxed context, the CVSS vector carries S:C (scope changed); the vector AV:N/AC:L/PR:L/UI:N/C:L/I:L/A:N confirms a network-reachable, low-complexity attack requiring only low-privilege (subscriber-level) authentication, with no user interaction needed by the victim to trigger the request that stores the payload.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Subscriber account needed (PR:L) but nonce protections are effectively bypassable (AC:L); stored XSS crosses into victims' browser context (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-86600
GHSA-22j7-2c3j-5wqh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB