# CVE-2026-113491: GeoDirectory < 2.8.194 - Subscriber+ Media File Disclosure and Deletion via Path Traversal


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-54m2-gc24-q2f7

## What is CVE-2026-113491?

CVE-2026-113491 is a medium-severity vulnerability in Unknown GeoDirectory, published on 24 Oct 2026. 

### Official description

The GeoDirectory  WordPress plugin before 2.8.194 does not validate a user-supplied image URL before using it as a local file path when saving a front-end listing, allowing users with Subscriber-level access and above to read files from outside the web root and to delete files on the server, limited to file names that carry an allowed media extension. A disclosed file is re-published at a public URL and its original is deleted as a side effect.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-113491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113491 is a medium-severity vulnerability in Unknown GeoDirectory, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113491 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-113491/ (Markdown: https://insights.sbomify.com/CVE-2026-113491/index.md)
```

## Sources

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

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