# CVE-2023-6777: WP Go Maps (formerly WP Google Maps) <= 9.0.34 - Information Exposure to Potential Denial of Service

> Unauthenticated attackers can obtain the developer's Google API key, potentially exhausting quota and causing denial of service for map functionality.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wfx2-88mh-r97m

## What is CVE-2023-6777?

CVE-2023-6777 is a medium-severity vulnerability in wpgmaps WP Go Maps (formerly WP Google Maps), published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-6777?

It affects 1 product.


Products: Codecabin Wp Go Maps.

## How do I fix CVE-2023-6777?

No fix has been published for CVE-2023-6777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6777 being exploited?

There is no known exploitation of CVE-2023-6777 in the wild and no public exploit code.

## Other vulnerabilities in wpgmaps WP Go Maps (formerly WP Google Maps)

- [CVE-2019-10692](https://insights.sbomify.com/CVE-2019-10692/): SQL injection in n/a (critical 9.8)
- [CVE-2024-29931](https://insights.sbomify.com/CVE-2024-29931/): WordPress WP Go Maps plugin <= 9.0.29 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-5994](https://insights.sbomify.com/CVE-2024-5994/): WP Go Maps (formerly WP Google Maps) <= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2024-3557](https://insights.sbomify.com/CVE-2024-3557/): WP Go Maps (formerly WP Google Maps) <= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 6.4)
- [CVE-2024-1582](https://insights.sbomify.com/CVE-2024-1582/): WP Go Maps (formerly WP Google Maps) <= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6777 and fix it if it is affected.

What it is: CVE-2023-6777 is a medium-severity vulnerability in wpgmaps WP Go Maps (formerly WP Google Maps), published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6777 in the wild and no public exploit code.

Affected product: wpgmaps WP Go Maps (formerly WP Google Maps). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6777/ (Markdown: https://insights.sbomify.com/CVE-2023-6777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6777
- OSV: https://osv.dev/vulnerability/CVE-2023-6777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6777/
Summaries are generated and may contain mistakes; the official description above is the record.