Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13359: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in stevejburge Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI

0
Medium
VulnerabilityCVE-2025-13359cvecve-2025-13359cwe-89
Published: Wed Dec 03 2025 (12/03/2025, 13:52:45 UTC)
Source: CVE Database V5
Vendor/Project: stevejburge
Product: Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 09:43:04 UTC

Technical Analysis

CVE-2025-13359 is a SQL Injection vulnerability classified under CWE-89 affecting the WordPress plugin 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' up to version 3.40.1. The vulnerability arises from insufficient escaping and preparation of SQL queries in the 'getTermsForAjax' function, which processes user-supplied parameters. Authenticated users with contributor-level privileges or higher can exploit this flaw because contributors have default metabox access to taxonomies, enabling them to inject additional SQL commands into existing queries. The injection is time-based, allowing attackers to infer data by measuring response delays, facilitating extraction of sensitive information from the backend database. The attack vector requires no user interaction beyond authentication, and the vulnerability does not affect integrity or availability but compromises confidentiality. While no known exploits are currently in the wild, the vulnerability's medium CVSS score (6.5) reflects its moderate ease of exploitation and potential impact. The plugin is used in WordPress sites that rely on AI-powered taxonomy management, making affected sites vulnerable to data breaches if unpatched.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive data stored in the WordPress database, including potentially user information, site configuration, or other confidential content. Since the vulnerability allows SQL Injection by authenticated contributors, attackers can leverage compromised or malicious contributor accounts to escalate data access without requiring administrator privileges. This can lead to privacy violations, intellectual property theft, or further pivoting within the network if database credentials or other sensitive data are exposed. Although the vulnerability does not directly affect data integrity or site availability, the confidentiality breach can undermine trust and compliance with data protection regulations. Organizations running WordPress sites with this plugin are at risk of targeted attacks, especially if contributor accounts are not tightly controlled or monitored.

Mitigation Recommendations

1. Immediately update the 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' plugin to a patched version once available. 2. If a patch is not yet available, restrict contributor-level access or disable metabox access for contributors to taxonomies to reduce attack surface. 3. Implement strict input validation and sanitization on all user-supplied parameters in the plugin's code, especially in the 'getTermsForAjax' function. 4. Employ Web Application Firewalls (WAFs) with SQL Injection detection rules tailored to WordPress environments to block suspicious queries. 5. Monitor logs for unusual database query patterns or timing anomalies indicative of time-based SQL Injection attempts. 6. Enforce the principle of least privilege for user roles, auditing contributor accounts regularly. 7. Consider database-level protections such as limiting the database user's permissions to only necessary operations. 8. Conduct security reviews and penetration testing focused on plugin vulnerabilities before deploying updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-18T15:56:36.915Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6930444551392e1c8b19b53b

Added to database: 12/3/2025, 2:08:05 PM

Last enriched: 2/27/2026, 9:43:04 AM

Last updated: 3/22/2026, 11:16:04 PM

Views: 104

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses