# CVE-2026-85200: GEO my WP <= 4.5.5.3 - Unauthenticated Local File Inclusion

> Unauthenticated attackers can exploit a Local File Inclusion vulnerability in the GEO my WP WordPress plugin to execute arbitrary PHP code or read sensitive data.

- **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:** 12 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-6hw9-7gx5-mw88

## What is CVE-2026-85200?

CVE-2026-85200 is a high-severity path traversal vulnerability in ninjew GEO my WP, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_ajax_info_window_loader function. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. In environments where PEAR is installed with register_argc_argv enabled, this file inclusion can be leveraged to write and execute arbitrary PHP code, achieving full remote code execution.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2026-85200 being exploited?

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

Public exploit code:

- GEO my WP <=4.5.5.3 - Unauthenticated Local File Inclusion (nuclei): http/cves/2026/CVE-2026-85200.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85200 is a high-severity path traversal vulnerability in ninjew GEO my WP, published on 12 Sep 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-85200 exists.

Affected product: ninjew GEO my WP. 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-85200/ (Markdown: https://insights.sbomify.com/CVE-2026-85200/index.md)
```

## Sources

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

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