CVE-2026-0593
Unauthorized Data Modification in WP Go Maps Plugin via Missing Capability Check
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_google_maps | wp_google_maps | to 10.0.04 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the WP Go Maps WordPress plugin allows authenticated users with Subscriber-level access or higher to modify global map engine settings without proper authorization. The issue is due to a missing capability check in the processBackgroundAction() function, which previously only verified POST parameters and a security nonce but did not confirm if the user had sufficient permissions. This flaw enables low-privilege users to perform privileged actions by exploiting AJAX request handlers. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing unauthorized users with low-level access (Subscriber or above) to change global map engine settings in the WP Go Maps plugin. This could lead to unauthorized modifications of your website's map configurations, potentially disrupting functionality or causing incorrect map data to be displayed to users. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring AJAX requests to the WordPress plugin 'wp-google-maps', specifically calls to the processBackgroundAction() function. Look for unauthorized AJAX POST requests that attempt to modify map engine settings without proper permission checks. Checking logs for AJAX requests lacking proper user capability verification or nonce validation may help. Since the vulnerability involves missing capability checks, you can also audit the plugin files for the presence or absence of the isUserAllowedToEdit() permission check in the class.admin-notices.php file. There are no specific commands provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the WP Go Maps plugin to a version later than 10.0.04 where the vulnerability is fixed. The fix involves adding a permission verification step using the isUserAllowedToEdit() method in AJAX request handlers to prevent unauthorized users from modifying map settings. Until you can update, restrict access to users with Subscriber-level access or higher from performing AJAX actions related to map engine settings, or disable the plugin temporarily to prevent exploitation. [1]