# CVE-2026-18032: WP Data Access < 5.5.79 - Unauthenticated Sensitive Data Disclosure via Autocomplete Column Authorization Bypass

> Unauthenticated attackers can read arbitrary database columns, including password hashes, due to missing authorization checks in the WP Data Access plugin.

- **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:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-chrp-6wq4-c4qg

## What is CVE-2026-18032?

CVE-2026-18032 is a high-severity vulnerability in Unknown WP Data Access, published on 9 Aug 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.79 does not validate the column names it accepts on one of its unauthenticated AJAX actions, and the nonce guarding that action does not cover them, allowing unauthenticated attackers to read arbitrary columns of the database table the affected front-end form is bound to, including user password hashes where that table is the users table.

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

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


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

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

## Is CVE-2026-18032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18032 is a high-severity vulnerability in Unknown WP Data Access, published on 9 Aug 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-18032 exists.

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-18032/ (Markdown: https://insights.sbomify.com/CVE-2026-18032/index.md)
```

## Sources

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

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