# CVE-2026-16988: GeoDirectory < 2.8.169 - Unauthenticated Pending/Draft Listing Disclosure via markers REST Endpoint

> Unauthenticated attackers can view titles and coordinates of pending or draft listings via the markers REST endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-9fxx-p9p4-4fjv

## What is CVE-2026-16988?

CVE-2026-16988 is a high-severity missing authorization vulnerability in Unknown GeoDirectory, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The GeoDirectory  WordPress plugin before 2.8.169 does not perform any authorization check when returning map marker data for a single requested listing, allowing unauthenticated users to disclose the title and exact geographic coordinates of non-public (pending or draft) listings.

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

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


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

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

## Is CVE-2026-16988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16988 is a high-severity missing authorization vulnerability in Unknown GeoDirectory, published on 9 Aug 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-16988 exists.

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

## Sources

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

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