# CVE-2025-13000: DB Access <= 0.8.7 - Subscriber+ SQLi

> Authenticated users can perform SQL injection attacks via an unprotected AJAX action in the DB Access WordPress plugin.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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:** 2 Dec 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-q93v-5jjx-7797

## What is CVE-2025-13000?

CVE-2025-13000 is a high-severity SQL injection vulnerability in Unknown db-access, published on 2 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The db-access WordPress plugin through 0.8.7 does not have authorization in an AJAX action, allowing any authenticated users, such as subscriber to perform SQLI attacks

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

## Which versions are affected by CVE-2025-13000?

It affects 1 product.


Products: Jimbob1953 Db-Access.

## How do I fix CVE-2025-13000?

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

## Is CVE-2025-13000 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13000 and fix it if it is affected.

What it is: CVE-2025-13000 is a high-severity SQL injection vulnerability in Unknown db-access, published on 2 Dec 2025. 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-2025-13000 exists.

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

## Sources

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

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