LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0593 affects the WP Go Maps WordPress plugin through version 10.0.04. A low-privileged logged-in user may change global map engine settings without proper authorization. This is not described as data theft or full site takeover, but it can affect site integrity and business presentation.

Executive priority

Treat as a routine but time-sensitive WordPress plugin remediation. Prioritize public-facing sites with user registration or many low-privileged accounts. This does not currently warrant emergency response unless unauthorized setting changes are observed.

Technical view

The issue is a missing capability check, CWE-862, in processBackgroundAction(). Sources describe authenticated Subscriber-level users and above being able to modify global map engine settings. The CVSS is 5.3 medium, though the provided vector lists PR:N, which conflicts with the authenticated-attack description.

Likely exposure

Exposure is most likely on WordPress sites running WP Go Maps / WP Google Maps version 10.0.04 or earlier, especially where subscribers, customers, contributors, or other low-privileged accounts exist. Sites without untrusted authenticated users have lower practical exposure.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires reaching the vulnerable plugin action and abusing missing authorization to change global map engine settings. Business impact is mainly unauthorized configuration change and integrity loss.

Researcher notes

Evidence identifies missing authorization in processBackgroundAction() and a related WordPress Trac changeset. The bundle does not name a fixed version. The CVSS vector’s privilege requirement conflicts with the narrative, so validation should rely on vendor details before exposure scoring.

Mitigation direction

  • Identify sites running WP Go Maps or WP Google Maps.
  • Prioritize sites on version 10.0.04 or earlier.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • Move affected sites off vulnerable versions when a fixed release is available.
  • Limit untrusted Subscriber-level accounts where operationally possible.
  • Review global map engine settings for unauthorized changes.

Validation and detection

  • Inventory plugin versions across WordPress sites.
  • Confirm whether any site runs version 10.0.04 or earlier.
  • Review low-privileged user registrations and account necessity.
  • Check map engine settings for unexpected changes.
  • Monitor Wordfence and plugin changelog for fix confirmation.
  • Validate updates in staging before production rollout.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0593 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-0593Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpgmapsWP Go Maps (formerly WP Google Maps)0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.