CVE-2025-13922 identifies a time-based blind SQL Injection vulnerability in the 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' WordPress plugin, versions up to and including 3.40.1. The vulnerability stems from insufficient sanitization and escaping of the 'existing_terms_orderby' parameter in the AI preview AJAX endpoint, combined with the absence of SQL query parameterization. This flaw allows authenticated attackers with at least Contributor-level access and AI metabox permissions to inject arbitrary SQL commands appended to legitimate queries. The injection is time-based blind, meaning attackers can infer data by measuring response delays, enabling extraction of sensitive database information without direct error messages. The vulnerability does not require user interaction beyond authentication and leverages the plugin's AJAX endpoint, which is accessible to users with specific permissions. The CVSS v3.1 score is 6.5 (medium), reflecting network attack vector, low attack complexity, required privileges, no user interaction, and high confidentiality impact but no integrity or availability impact. No known public exploits exist yet, but the vulnerability could be leveraged to compromise data confidentiality, degrade performance, or conduct further attacks. The root cause is the lack of proper input validation and failure to use parameterized queries in the plugin's codebase. This vulnerability highlights the risks of insufficient input handling in WordPress plugins, especially those integrating AI features and complex taxonomy management.

The primary impact of this vulnerability is unauthorized disclosure of sensitive information stored in the WordPress database, including potentially user data, site configuration, and content metadata. Attackers with Contributor-level access can exploit this flaw to extract data without needing higher privileges, increasing the attack surface. The time-based blind SQL Injection technique allows attackers to infer data slowly, making detection difficult and enabling stealthy data exfiltration. Additionally, injected queries can degrade database performance, potentially impacting site responsiveness and availability indirectly. While the vulnerability does not allow direct modification or deletion of data (no integrity or availability impact), the confidentiality breach can lead to further attacks such as privilege escalation or targeted phishing. Organizations running WordPress sites with this plugin, especially those handling sensitive or regulated data, face increased risk of data leaks and reputational damage. The requirement for authenticated access limits exposure but does not eliminate risk, as Contributor accounts are common in multi-user WordPress environments. The absence of known exploits currently reduces immediate threat but proactive mitigation is critical to prevent future exploitation.

1. Immediate mitigation includes restricting Contributor-level user permissions and AI metabox access to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 2. Monitor and audit Contributor account activities and database query logs for unusual or time-delayed responses indicative of exploitation attempts. 3. Implement web application firewall (WAF) rules to detect and block suspicious SQL Injection patterns targeting the 'existing_terms_orderby' parameter in AJAX requests. 4. Encourage plugin developers or site administrators to apply patches or updates as soon as they become available; if no patch exists, consider temporarily disabling the plugin or the vulnerable feature. 5. Review and harden WordPress security configurations, including limiting plugin installations and enforcing strong authentication policies. 6. For developers, refactor plugin code to use parameterized queries and proper input validation and escaping to prevent SQL Injection. 7. Conduct regular security assessments and penetration testing focusing on plugins with elevated permissions and database interactions. 8. Educate site administrators about the risks of granting Contributor-level access and the importance of least privilege principles.