CVE-2023-6777

WP Go Maps (formerly WP Google Maps) <= 9.0.34 - Information Exposure to Potential Denial of Service

Strategic Overview

Status
Patched in 9.0.35
Affected Version
<= 9.0.34
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-6777
View all WP Go Maps – Google Map, OpenStreetMap, Leaflet Map vulnerabilities

At a glance

CVE-2023-6777 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 9.0.34. 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 9.0.35; sites on affected versions should update now. Disclosed March 2024, reported by Hassan Khan Yusufzai - Splint3r7.

Vulnerability Overview

The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to unauthenticated API key disclosure in versions up to, and including, 9.0.34 due to the plugin adding the API key to several plugin files. This makes it possible for unauthenticated attackers to obtain the developer's Google API key. While this does not affect the security of sites using this plugin, it allows unauthenticated attackers to make requests using this API key with the potential of exhausting requests resulting in an inability to use the map functionality offered by the plugin.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WP Go Maps <= 9.0.34 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Go Maps the fix is 9.0.35: builds <= 9.0.34 are affected, anything from 9.0.35 onward is not.

Remediation

Update to version 9.0.35, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP Go Maps 9.0.35 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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