CVE-2025-13359 MEDIUM

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

Vendor Stevejburge
Product Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI
Weakness CWE-89 · SQLi
Published December 3, 2025
Last update April 8, 2026

CVSS base score

6.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

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).

Explanation of Vulnerability in Simple Terms

02Summary

The Tag, Category, and Taxonomy Manager plugin for WordPress contains a SQL injection vulnerability in versions up to 3.40.1. An authenticated user with low privileges can craft malicious input to execute arbitrary SQL queries against the site's database. This allows reading sensitive data without modifying or deleting records. The vulnerability requires a valid WordPress account but no additional user interaction.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site's database, including user information and configuration details.

Potential impact on your site

04Site Impact

User data and site configuration may be exposed to anyone with basic WordPress access; immediate patching required.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

December 3, 2025 CVE published
April 8, 2026 Record updated