# CVE-2026-106470: WP Data Access < 5.5.88 - Subscriber+ SSRF

> Authenticated users can exploit missing authorization to force the server to connect to arbitrary internal or external hosts and read responses.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-jmr2-v244-x8cp

## What is CVE-2026-106470?

CVE-2026-106470 is a medium-severity server-side request forgery vulnerability in Unknown WP Data Access, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Data Access  WordPress plugin before 5.5.88 does not have authorisation and CSRF checks in one of its actions, allowing any authenticated user, such as a subscriber, to make the server open connections to arbitrary hosts and ports, including internal ones, and read back the outcome.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-106470 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106470 is a medium-severity server-side request forgery vulnerability in Unknown WP Data Access, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106470 in the wild and no public exploit code.

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

## Sources

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

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