# CVE-2026-106099: WP Data Access < 5.5.84 - Unauthenticated Sensitive Data Disclosure via Table Export

> Unauthenticated attackers can export complete database table contents, including hidden columns, by exploiting insufficient access controls in the WP Data Access plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-mjx7-qq55-q3w6

## What is CVE-2026-106099?

CVE-2026-106099 is a medium-severity missing authorization vulnerability in Unknown WP Data Access, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Data Access  WordPress plugin before 5.5.84 does not restrict its database table export action to authorized users, gating it only with a token that the WP Data Access  WordPress plugin before 5.5.84 itself prints into the public pages on which it displays a table, allowing unauthenticated attackers to export the complete contents of any publicly displayed table, including columns and rows withheld from the display shown to visitors.

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

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


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

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

## Is CVE-2026-106099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106099 is a medium-severity missing authorization vulnerability in Unknown WP Data Access, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106099 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-106099/ (Markdown: https://insights.sbomify.com/CVE-2026-106099/index.md)
```

## Sources

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

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