CVE-2025-13354: 
WordPress vulnerability analysis and mitigation

CVE-2025-13354 is an authorization bypass vulnerability in the Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI plugin for WordPress (also known as TaxoPress). It affects all versions up to and including 3.40.1, allowing authenticated attackers with subscriber-level access or higher to merge or delete arbitrary taxonomy terms without proper authorization checks. The vulnerability was published on December 3, 2025, and a patch was released in version 3.41.0. It carries a CVSS v3.1 base score of 4.3 (Medium) (Wordfence, Red Hat CVE).

The root cause is classified as CWE-862 (Missing Authorization). Specifically, the taxopress_merge_terms_batch function in inc/class.admin.manage.php only verified a nonce for CSRF protection but failed to check whether the authenticated user had the required capability (simple_tags) to perform the merge or delete operation. The fix, committed in GitHub commit 5eb2cee, adds an explicit current_user_can('simple_tags') check after nonce validation, returning a 403 error for unauthorized users. The attack vector is network-based, requires low privileges (subscriber account), no user interaction, and low attack complexity (Wordfence, GitHub Commit).

Successful exploitation allows any authenticated user with at least subscriber-level access to merge or delete arbitrary taxonomy terms (tags, categories, custom taxonomies) on the affected WordPress site. This can disrupt content organization, corrupt site categorization structures, and cause unintended loss of taxonomy data. While there is no direct confidentiality or availability impact, the integrity of the site's content taxonomy is at risk, potentially affecting SEO, navigation, and content discoverability (Wordfence, Red Hat CVE).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.026% (0.000260), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a valid authenticated account on the target WordPress site, limiting opportunistic mass exploitation (Wordfence).

1. Reconnaissance: Identify WordPress sites running the TaxoPress plugin (version ≤ 3.40.1) by checking plugin headers, readme files, or using tools like WPScan.
2. Obtain authenticated access: Register or log in as a subscriber-level (or higher) user on the target WordPress site.
3. Obtain a valid nonce: Load any admin page that includes the st-admin-js nonce, or trigger a legitimate AJAX request to capture the nonce value from the page source or network traffic.
4. Craft malicious AJAX request: Send a POST request to the WordPress AJAX endpoint (/wp-admin/admin-ajax.php) targeting the taxopress_merge_terms_batch action, including the captured nonce and the IDs of taxonomy terms to merge or delete.
5. Achieve unauthorized modification: The server processes the request without verifying the user's capability, resulting in arbitrary taxonomy terms being merged or deleted (GitHub Commit, Wordfence).

• Network: Unexpected POST requests from low-privilege user accounts to /wp-admin/admin-ajax.php with the action parameter set to taxopress_merge_terms_batch.
• Logs: WordPress access logs showing repeated AJAX calls to admin-ajax.php from subscriber-level accounts, particularly with taxonomy merge/delete parameters outside of normal administrative hours.
• Application: Unexplained disappearance or merging of taxonomy terms (tags, categories) in the WordPress database (wp_terms, wp_term_taxonomy tables) without corresponding admin activity.
• Database: Audit of wp_terms and wp_term_taxonomy tables for unexpected deletions or merges not attributable to administrator actions.

Update the TaxoPress plugin to version 3.41.0 or later, which adds a proper current_user_can('simple_tags') capability check in the taxopress_merge_terms_batch function. No configuration-based workaround is available; upgrading is the only effective remediation. Site administrators should also review recent taxonomy changes for signs of unauthorized modification and audit user accounts with subscriber-level access (GitHub Commit, Wordfence).

The vulnerability was discovered and reported by Wordfence, which published the advisory on December 3, 2025. Sucuri included it in their December 2025 vulnerability patch roundup, noting it as part of a broader set of WordPress plugin issues addressed that month (Sucuri Blog). No significant broader media coverage or notable researcher commentary beyond standard vulnerability tracking has been observed.