# CVE-2026-113494: GeoDirectory < 2.8.195 - Contributor+ Non-Public Listing Disclosure via gd_post_content Shortcode


- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-4562-6r2h-7rvw

## What is CVE-2026-113494?

CVE-2026-113494 is a low-severity vulnerability in Unknown GeoDirectory, published on 28 Oct 2026. 

### Official description

The GeoDirectory  WordPress plugin before 2.8.195 does not perform any status or ownership check when rendering a listing referenced by an id attribute in its field shortcodes, allowing users with the Contributor role and above to disclose the content and custom fields of other users' draft, pending, private and trashed listings.

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

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


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

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

## Is CVE-2026-113494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113494 is a low-severity vulnerability in Unknown GeoDirectory, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113494 in the wild and no public exploit code.

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-113494/ (Markdown: https://insights.sbomify.com/CVE-2026-113494/index.md)
```

## Sources

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

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