The vulnerability CVE-2025-13922 affects the 'Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI' WordPress plugin, versions up to and including 3.40.1. It is a time-based blind SQL Injection flaw caused by insufficient escaping and lack of parameterization of the 'existing_terms_orderby' parameter in the AI preview AJAX endpoint. Authenticated attackers with Contributor-level access and AI metabox permissions can inject arbitrary SQL commands appended to legitimate queries. This allows them to extract sensitive information from the database by measuring response times, potentially leading to data leakage. The vulnerability does not require user interaction but does require authentication with specific permissions, limiting the attack surface to insiders or compromised accounts. The flaw does not directly affect data integrity or availability but can cause performance degradation and information disclosure. No patches are currently linked, and no known exploits have been observed in the wild. The CVSS 3.1 score is 6.5 (medium), reflecting network attack vector, low complexity, privileges required, no user interaction, and high confidentiality impact. The vulnerability falls under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).

For European organizations, this vulnerability poses a significant risk to WordPress sites using the affected plugin, especially those that allow Contributor-level users to access AI metabox features. Successful exploitation can lead to unauthorized disclosure of sensitive data stored in the WordPress database, including user information, site configuration, or other confidential content. This can result in privacy violations under GDPR and damage organizational reputation. Performance degradation caused by injected queries may disrupt site availability temporarily, impacting business operations and user experience. Since the attack requires authenticated access, insider threats or compromised Contributor accounts are primary concerns. Organizations relying heavily on WordPress for content management and AI tagging functionalities are particularly vulnerable. The lack of current patches increases exposure time, emphasizing the need for immediate mitigation. The medium severity indicates a moderate but actionable threat level.

1. Immediately restrict Contributor-level user permissions, especially revoking AI metabox access until a patch is available. 2. Monitor and audit Contributor account activities for unusual behavior or access patterns. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious SQL injection payloads targeting the 'existing_terms_orderby' parameter in AJAX requests. 4. Employ database query logging and anomaly detection to identify time-based delays indicative of blind SQL Injection attempts. 5. Keep WordPress core and all plugins updated; apply vendor patches promptly once released for this vulnerability. 6. Consider disabling or removing the vulnerable plugin if AI autotagging is not critical to operations. 7. Use principle of least privilege for all user roles and regularly review user permissions. 8. Educate site administrators and developers about secure coding practices and the risks of SQL Injection. 9. Backup databases regularly to enable recovery in case of data compromise. 10. Engage with the plugin vendor or community to track patch releases and vulnerability disclosures.