# CVE-2026-8385: WP Go Maps < 10.0.10 - Unauthenticated Sensitive Information Disclosure via Datatables AJAX Fallback

> Unauthenticated attackers can access unapproved marker details via an AJAX fallback, exposing sensitive location data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-f9fr-2hr3-67mf

## What is CVE-2026-8385?

CVE-2026-8385 is a medium-severity vulnerability in Unknown WP Go Maps, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Go Maps  WordPress plugin before 10.0.10 does not properly enforce the marker approval filter on the admin-ajax fallback for its datatables route, allowing unauthenticated visitors to retrieve marker records that the site owner has not approved for public display, including their title, category, address and description fields.

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

## Which versions are affected by CVE-2026-8385?


## How do I fix CVE-2026-8385?

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

## Is CVE-2026-8385 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8385 exists.

Public exploit code:

- WordPress WP Go Maps < 10.0.10 - Unauthenticated Marker Data Disclosure (nuclei): http/cves/2026/CVE-2026-8385.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8385 and fix it if it is affected.

What it is: CVE-2026-8385 is a medium-severity vulnerability in Unknown WP Go Maps, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8385 exists.

Affected product: Unknown WP Go 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-2026-8385/ (Markdown: https://insights.sbomify.com/CVE-2026-8385/index.md)
```

## Sources

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

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