CVE-2026-8732: WP Maps Pro WordPress Vulnerability
Critical CVSS (9.8) reachable over network.
TL;DR - CVE-2026-8732 is a critical WP Maps Pro vulnerability that allows unauthenticated attackers to create WordPress administrator accounts. - WP Maps Pro 6.1.0 and earlier are affected. Upgrade to 6.1.1 or later immediately. - Exploitation has been reported in the wild. Investigate exposed sites even after applying the patch.
Are You Affected?
CVE-2026-8732 affects the WP Maps Pro WordPress plugin, also distributed as the Advanced Google Maps Plugin for WordPress. The affected WordPress plugin slug is reported as wp-google-map-gold.
| Field | Detail |
|---|---|
| CVE | CVE-2026-8732 |
| CVSS | 9.8 Critical |
| Attack vector | Network |
| Authentication required | None |
| Privileges required | None |
| User interaction | None, based on the supplied severity assessment |
| Impact | High confidentiality, integrity, and availability impact |
| Affected versions | WP Maps Pro 6.1.0 and earlier |
| Fixed version | WP Maps Pro 6.1.1 |
| Patch available | Yes |
| CISA KEV | Not listed as of 2026-11-13 |
Every installation running version 6.1.0 or earlier should be considered vulnerable if the plugin is active and reachable through the public WordPress site. The issue is not limited to a particular hosting provider or deployment model.
For broader WordPress security guidance, see our FAQ on securing WordPress and Zoom meetings and our CVE-2026-94083 vulnerability analysis.
The supplied NVD response does not include the complete CVSS vector string. The 9.8 score is consistent with an unauthenticated, remotely reachable, low-complexity attack that requires no user interaction and can affect confidentiality, integrity, and availability. The absence of a CISA KEV listing does not mean an installation is safe or that exploitation has not occurred.
The Fix, If You’re in a Hurry
Upgrade WP Maps Pro to 6.1.1 or later immediately. Version 6.1.1 is identified as the fixed release and was reported as released on May 20, 2026. Verify the installed version from the WordPress plugins page, deployment inventory, or plugin files rather than relying only on a package manager’s intended state.
If the plugin cannot be upgraded promptly, deactivate or remove it. Deactivation prevents the plugin’s vulnerable functionality from executing, although administrators should still investigate whether the site was previously attacked. Removing the plugin may affect map content or site functionality, so preserve a backup and document the change first.
Technical Notes: Mitigation
For a WP-CLI-managed installation, check the current version and update the plugin with:
wp plugin get wp-google-map-gold --field=version
wp plugin update wp-google-map-gold
wp plugin get wp-google-map-gold --field=version
Confirm that the resulting version is 6.1.1 or later. If an update is not immediately possible, deactivate the plugin:
wp plugin deactivate wp-google-map-gold
If the plugin is not available through the expected update channel, obtain version 6.1.1 or later from the product’s authorized distribution source and validate the package before installation. Do not use an unverified third-party archive.
Because successful exploitation creates an administrator account and can establish an authenticated session, remediation must include incident response. Review recently created users, administrator role assignments, WordPress salts and secrets, active sessions, API keys, plugins, themes, uploads, and scheduled tasks. Rotate administrator credentials and WordPress salts after preserving evidence where possible.
How This Vulnerability Works
The vulnerability is an administrator-account-creation flaw in WP Maps Pro. The plugin registers an AJAX action for unauthenticated requests through WordPress’s wp_ajax_nopriv_ mechanism, making the functionality reachable by visitors who are not logged in.
The handler checks a nonce named fc-call-nonce, but the nonce is exposed on public frontend pages through the wp_localize_script object wpgmp_local. A nonce exposed to an unauthenticated visitor is not an authorization boundary. It can help protect against some cross-site request forgery scenarios, but it does not establish that the requester is an administrator.
The relevant AJAX action and handler are:
AJAX action: wpgmp_temp_access_ajax
Handler: wpgmp_temp_access_support
Parameter: check_temp=false
Nonce field: fc-call-nonce
Frontend data: wpgmp_local
When the handler receives the relevant request with check_temp=false, the vulnerable code path can create a WordPress account using wp_insert_user(). It assigns the new account the hardcoded administrator role and returns a magic login URL. Visiting that URL invokes wp_set_auth_cookie(), allowing the attacker to authenticate as the newly created administrator.
This is a complete privilege-escalation and site-takeover path, not merely an information disclosure issue. A successful attacker can modify content, install or alter plugins and themes, create additional accounts, access site data, and use the WordPress installation to attack visitors or other systems.
Technical Notes: Root Cause
The security boundary fails because an endpoint intended for temporary support access is reachable without authentication, while the exposed nonce is treated as if it provided authorization. The dangerous sequence is:
Unauthenticated request
-> public nonce obtained from frontend
-> wpgmp_temp_access_ajax
-> wpgmp_temp_access_support
-> check_temp=false
-> wp_insert_user(... role=administrator)
-> magic login URL
-> wp_set_auth_cookie()
The reported fix adds an authorization and capability check so that the relevant endpoint requires an already authenticated administrator. That check matters because a nonce cannot replace authentication and authorization for an account-creation operation.
Analyst’s Take: Patch or deactivate the plugin before treating this as a routine plugin update. The exposed nonce does not prevent unauthenticated access, and reported exploitation means version verification should be followed by account and log review.
Severity, Explained
CVE-2026-8732 has a reported CVSS base score of 9.8, Critical. The practical reason for that rating is the combination of public network reachability, no required credentials, no required user interaction, and the ability to create a WordPress administrator account.
The supplied NVD response does not provide the full CVSS vector string, so the exact individual metric encoding should not be reconstructed as an official vector. Based on the supplied assessment, the relevant characteristics are:
| CVSS characteristic | Practical meaning |
|---|---|
| Network attack vector | The attack can be sent remotely over the web |
| No privileges required | The attacker does not need a WordPress account |
| No user interaction | The victim does not need to click or approve anything |
| Low attack complexity | The exploit path is straightforward once the endpoint and request parameters are known |
| High confidentiality impact | An administrator can access protected site and application data |
| High integrity impact | An administrator can modify content, code, configuration, and users |
| High availability impact | An administrator can disrupt or destroy site functionality |
The vulnerability is particularly serious for small businesses and managed WordPress environments because one compromised site can expose customer data, payment integrations, email configuration, API credentials, and other connected services.
Is It Being Exploited?
Independent reporting states that exploitation has been observed in the wild. SecurityWeek reported that Defiant observed and blocked more than 1,700 attacks targeting CVE-2026-8732 over a 24-hour period. That reporting should drive immediate remediation for internet-facing installations.
The CVE is not currently listed in CISA’s Known Exploited Vulnerabilities catalog. The available CISA result is:
on_kev: false
cve_id: CVE-2026-8732
This means no CISA dateAdded, remediation dueDate, required action, or ransomware-campaign flag is available for this CVE at the time of assessment. It does not mean exploitation has not happened. CISA KEV inclusion and independent observations are separate signals.
A verified public GitHub proof-of-concept repository was not identified in the supplied research. NVD describes the technical attack chain but does not attach a public exploit repository or proof-of-concept link. The absence of a verified public repository should not lower urgency: the endpoint is unauthenticated, the nonce is publicly exposed, and active exploitation has been reported.
Detecting It in Your Environment
Start by identifying every WordPress site with WP Maps Pro installed, including sites managed outside the central IT inventory. Check active and inactive copies, staging systems that are internet-accessible, and backups or cloned environments that may have been restored into production.
For each site, review the WordPress user table for unexpected accounts created during or after the period in which version 6.1.0 or earlier was active. Pay particular attention to newly created administrator accounts, unfamiliar usernames or email addresses, accounts with recently changed roles, and login activity associated with those accounts. Preserve logs before deleting suspicious users.
Technical Notes: Log Patterns and Queries
Search web-server access logs for requests containing the vulnerable AJAX action and parameter. URL encoding and request methods vary, so search for both the action name and the handler-related parameter:
zgrep -E 'wpgmp_temp_access_ajax|check_temp([=%]|%3D)' /var/log/nginx/access.log*
For Apache environments:
zgrep -E 'wpgmp_temp_access_ajax|check_temp([=%]|%3D)' /var/log/apache2/access.log*
A representative suspicious request may contain patterns similar to:
POST /wp-admin/admin-ajax.php?action=wpgmp_temp_access_ajax
...check_temp=false...
The exact request format can vary by exploit tooling, proxy, web server, and encoding. Do not rely on one complete string match. Search for admin-ajax.php, wpgmp_temp_access_ajax, and check_temp independently, then correlate timestamps, source addresses, response codes, and subsequent WordPress logins.
If your web application firewall or SIEM supports structured queries, a starting point is:
http.request.uri contains "/wp-admin/admin-ajax.php"
and http.request.uri contains "wpgmp_temp_access_ajax"
Correlate matches with WordPress authentication events, new-user events, and changes to administrator roles. Also inspect subsequent requests for /wp-login.php, /wp-admin/, plugin installation, theme editing, file uploads, or changes to user accounts.
Post-Compromise Checks
Review the WordPress users table for administrator accounts created during the exposure window. Preserve relevant records before removal, including user ID, username, email address, creation timestamp if available, role assignments, and associated metadata.
Inspect recently modified PHP files in wp-content/plugins, wp-content/themes, wp-content/uploads, and the WordPress root. Check scheduled tasks, mu-plugins, database options, and web-server configuration for persistence. Rotate WordPress salts and secrets in wp-config.php, administrator passwords, API keys, database credentials where appropriate, and active sessions.
If evidence indicates successful compromise, consider rebuilding the site from a known-clean source rather than assuming that deleting one unauthorized account removes attacker access.
References and Further Reading
The primary CVE record is available from CVE.org:
The NVD references identify the affected product distribution and principal vulnerability advisory:
- Advanced Google Maps Plugin for WordPress on CodeCanyon
- Wordfence vulnerability advisory for CVE-2026-8732
Additional reporting and technical context are available from:
- Wordfence: WP Maps Pro administrator account creation vulnerability
- AhnLab ASEC advisory
- SecurityWeek reporting on exploitation
Treat WP Maps Pro 6.1.0 and earlier as exposed. Upgrade to 6.1.1 or later immediately. If that cannot be done, deactivate or remove the plugin and investigate accounts, logs, files, scheduled tasks, and credentials. Although CVE-2026-8732 is not currently in CISA KEV, reported exploitation makes patching and incident response urgent.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.