CVE-2026-0593

WP Go Maps (formerly WP Google Maps) <= 10.0.04 - Missing Authorization to Authenticated (Subscriber+) Map Engine Setting Modification

2026-01-24 04:04
Moose Love

Strategic Overview

Status
Patched in 10.0.05
Affected Plugin
WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
Affected Version
<= 10.0.04
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-0593
View all WP Go Maps – Google Map, OpenStreetMap, Leaflet Map vulnerabilities

At a glance

CVE-2026-0593 is a medium-severity Missing Authorization vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 10.0.04. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.0.05; sites on affected versions should update now. Disclosed January 2026, reported by Moose Love.

Vulnerability Overview

The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the processBackgroundAction() function in all versions up to, and including, 10.0.04. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify global map engine settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

WP Go Maps <= 10.0.04 carries this weakness at processBackgroundAction(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Go Maps the fix is 10.0.05: builds <= 10.0.04 are affected, anything from 10.0.05 onward is not.

Remediation

Update to version 10.0.05, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Go Maps 10.0.05 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0593https://www.wordfence.com/threat-intel/vulnerabilities/id/7f0741c1-a5d7-41a4-a739-2cb7cb836509https://nvd.nist.gov/vuln/detail/CVE-2026-0593

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C