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
CVE-2025-13359 is a medium severity SQL Injection vulnerability in the WordPress plugin 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' affecting all versions up to 3. 40. 1. Authenticated users with contributor-level access or higher can exploit insufficient input sanitization in the getTermsForAjax function to perform time-based SQL Injection attacks. This allows attackers to append malicious SQL queries and extract sensitive database information without requiring user interaction. The vulnerability impacts confidentiality but does not affect integrity or availability. No known exploits are currently reported in the wild. European organizations using this plugin on WordPress sites should prioritize patching or mitigating this flaw to prevent data leakage. Countries with high WordPress adoption and active content management workflows, such as Germany, France, and the UK, are most likely to be affected.
AI Analysis
Technical Summary
CVE-2025-13359 is a SQL Injection vulnerability classified under CWE-89 found in the 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' WordPress plugin, versions up to and including 3.40.1. The vulnerability arises from improper neutralization of special elements in SQL commands within the getTermsForAjax function. Specifically, user-supplied parameters are not properly escaped or prepared before being incorporated into SQL queries, enabling authenticated users with contributor-level privileges or higher to inject additional SQL commands. Since contributors have metabox access to taxonomies by default, they can exploit this flaw to perform time-based blind SQL Injection attacks, extracting sensitive data from the underlying database. The attack vector is remote over the network, requires low attack complexity, and does not require user interaction. The vulnerability impacts confidentiality by allowing unauthorized data disclosure but does not affect data integrity or system availability. No patches or exploit code are currently publicly available, and no known active exploitation has been reported. The CVSS v3.1 base score is 6.5, reflecting medium severity with network attack vector, low complexity, and privileges required but no user interaction.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive data stored in WordPress databases, including potentially user information, content metadata, and configuration details. Since contributors can exploit this flaw, insider threats or compromised contributor accounts could lead to data leakage. Organizations relying on this plugin for content categorization and AI-assisted tagging may face exposure of proprietary or personal data, potentially violating GDPR and other data protection regulations. Although the vulnerability does not directly impact availability or integrity, the unauthorized disclosure of data can damage organizational reputation and lead to regulatory penalties. The risk is heightened for organizations with large editorial teams or those that grant contributor-level access broadly. Additionally, the lack of known exploits in the wild suggests a window of opportunity for proactive mitigation before attackers develop weaponized exploits.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to identify the presence of the vulnerable 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' plugin. Since no official patches are currently available, temporary mitigations include restricting contributor-level access to trusted users only and disabling metabox access for taxonomies if feasible. Implementing Web Application Firewall (WAF) rules to detect and block suspicious SQL injection patterns targeting the getTermsForAjax function can reduce risk. Monitoring database query logs for anomalous or time-based delays may help detect exploitation attempts. Organizations should also follow the plugin vendor’s updates closely for forthcoming patches and apply them promptly. Additionally, enforcing strong authentication and monitoring contributor account activities can limit the potential for abuse. Finally, consider isolating WordPress database access with least privilege principles to minimize data exposure if exploitation occurs.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland
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
Description
CVE-2025-13359 is a medium severity SQL Injection vulnerability in the WordPress plugin 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' affecting all versions up to 3. 40. 1. Authenticated users with contributor-level access or higher can exploit insufficient input sanitization in the getTermsForAjax function to perform time-based SQL Injection attacks. This allows attackers to append malicious SQL queries and extract sensitive database information without requiring user interaction. The vulnerability impacts confidentiality but does not affect integrity or availability. No known exploits are currently reported in the wild. European organizations using this plugin on WordPress sites should prioritize patching or mitigating this flaw to prevent data leakage. Countries with high WordPress adoption and active content management workflows, such as Germany, France, and the UK, are most likely to be affected.
AI-Powered Analysis
Technical Analysis
CVE-2025-13359 is a SQL Injection vulnerability classified under CWE-89 found in the 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' WordPress plugin, versions up to and including 3.40.1. The vulnerability arises from improper neutralization of special elements in SQL commands within the getTermsForAjax function. Specifically, user-supplied parameters are not properly escaped or prepared before being incorporated into SQL queries, enabling authenticated users with contributor-level privileges or higher to inject additional SQL commands. Since contributors have metabox access to taxonomies by default, they can exploit this flaw to perform time-based blind SQL Injection attacks, extracting sensitive data from the underlying database. The attack vector is remote over the network, requires low attack complexity, and does not require user interaction. The vulnerability impacts confidentiality by allowing unauthorized data disclosure but does not affect data integrity or system availability. No patches or exploit code are currently publicly available, and no known active exploitation has been reported. The CVSS v3.1 base score is 6.5, reflecting medium severity with network attack vector, low complexity, and privileges required but no user interaction.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive data stored in WordPress databases, including potentially user information, content metadata, and configuration details. Since contributors can exploit this flaw, insider threats or compromised contributor accounts could lead to data leakage. Organizations relying on this plugin for content categorization and AI-assisted tagging may face exposure of proprietary or personal data, potentially violating GDPR and other data protection regulations. Although the vulnerability does not directly impact availability or integrity, the unauthorized disclosure of data can damage organizational reputation and lead to regulatory penalties. The risk is heightened for organizations with large editorial teams or those that grant contributor-level access broadly. Additionally, the lack of known exploits in the wild suggests a window of opportunity for proactive mitigation before attackers develop weaponized exploits.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to identify the presence of the vulnerable 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' plugin. Since no official patches are currently available, temporary mitigations include restricting contributor-level access to trusted users only and disabling metabox access for taxonomies if feasible. Implementing Web Application Firewall (WAF) rules to detect and block suspicious SQL injection patterns targeting the getTermsForAjax function can reduce risk. Monitoring database query logs for anomalous or time-based delays may help detect exploitation attempts. Organizations should also follow the plugin vendor’s updates closely for forthcoming patches and apply them promptly. Additionally, enforcing strong authentication and monitoring contributor account activities can limit the potential for abuse. Finally, consider isolating WordPress database access with least privilege principles to minimize data exposure if exploitation occurs.
Affected Countries
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: 12/10/2025, 2:52:46 PM
Last updated: 1/18/2026, 1:42:12 AM
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1107: Unrestricted Upload in EyouCMS
MediumCVE-2026-1106: Improper Authorization in Chamilo LMS
MediumCVE-2026-1105: SQL Injection in EasyCMS
MediumCVE-2026-1066: Command Injection in kalcaddle kodbox
MediumCVE-2026-1064: Command Injection in bastillion-io Bastillion
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.