# CVE-2026-16263: WP Maps < 4.9.7 - Subscriber+ Local File Inclusion

> Subscribers can exploit a missing capability check and path validation flaw to include and execute arbitrary local PHP files, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-v8wm-6qmw-j72p

## What is CVE-2026-16263?

CVE-2026-16263 is a high-severity path traversal vulnerability in Unknown WP Maps, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Maps  WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not properly validate a user-controlled path before using it in a file inclusion, allowing users with a Subscriber account to include and execute arbitrary existing local PHP files on the server.

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

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


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

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

## Is CVE-2026-16263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16263 is a high-severity path traversal vulnerability in Unknown WP Maps, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16263 exists.

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

## Sources

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

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