# CVE-2025-13359: Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection

> Authenticated contributors can exploit SQL injection in the AI Autotagger plugin to extract sensitive database information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 3 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q5c3-w3j7-4hxr

## What is CVE-2025-13359?

CVE-2025-13359 is a medium-severity SQL injection vulnerability in stevejburge Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI plugin for WordPress is vulnerable to time-based SQL Injection via the "getTermsForAjax"  function in all versions up to, and including, 3.40.1. This is due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database granted they have metabox access for the taxonomy (enabled by default for contributors).

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

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

It affects 1 product.


Products: Taxopress Taxopress.

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

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

## Is CVE-2025-13359 being exploited?

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

## Other vulnerabilities in stevejburge Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI

- [CVE-2023-2168](https://insights.sbomify.com/CVE-2023-2168/): TaxoPress <= 3.6.4 - Authenticated (Editor+) Stored Cross-Site Scripting (medium 5.5)
- [CVE-2023-2169](https://insights.sbomify.com/CVE-2023-2169/): TaxoPress <= 3.6.4 - Authenticated (Editor+) Stored Cross-Site Scripting (medium 5.5)
- [CVE-2023-2170](https://insights.sbomify.com/CVE-2023-2170/): TaxoPress <= 3.6.4 - Authenticated (Editor+) Stored Cross-Site Scripting (medium 5.5)
- [CVE-2021-24444](https://insights.sbomify.com/CVE-2021-24444/): TaxoPress < 3.0.7.2 - Authenticated Stored Cross-Site Scripting (XSS) (medium 4.8)
- [CVE-2025-13354](https://insights.sbomify.com/CVE-2025-13354/): Missing authorization in Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13359 is a medium-severity SQL injection vulnerability in stevejburge Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13359 in the wild and no public exploit code.

Affected product: stevejburge Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI. 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-13359/ (Markdown: https://insights.sbomify.com/CVE-2025-13359/index.md)
```

## Sources

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

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