# CVE-2026-93621: WordPress WP Data Access plugin <= 5.5.84 - SQL Injection vulnerability

> Unauthenticated attackers can execute arbitrary SQL commands via the WP Data Access plugin, potentially reading or modifying database contents.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-5g83-hrq4-3rpq

## What is CVE-2026-93621?

CVE-2026-93621 is a high-severity SQL injection vulnerability in Passionate Programmer Peter WP Data Access, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated SQL Injection in WP Data Access <= 5.5.84 versions.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-93621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93621 is a high-severity SQL injection vulnerability in Passionate Programmer Peter WP Data Access, published on 30 Sep 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-93621 in the wild and no public exploit code.

Affected product: Passionate Programmer Peter 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-93621/ (Markdown: https://insights.sbomify.com/CVE-2026-93621/index.md)
```

## Sources

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

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