CVE-2025-14371

TaxoPress <= 3.41.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Tag Modification

2026-01-05 19:03
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 3.42.0
Affected Plugin
Tag, Category, and Taxonomy Manager – Autotagger Automatically Add Terms
Affected Version
<= 3.41.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-14371
View all Tag, Category, and Taxonomy Manager – Autotagger Automatically Add Terms vulnerabilities

At a glance

CVE-2025-14371 is a medium-severity Missing Authorization vulnerability in the Tag, Category, and Taxonomy Manager WordPress plugin, affecting versions <= 3.41.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.42.0; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the taxopress_ai_add_post_term function in all versions up to, and including, 3.41.0. This makes it possible for authenticated attackers, with Contributor-level access and above, to add or remove taxonomy terms (tags, categories) on any post, including ones they do not own.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Tag, Category, and Taxonomy Manager <= 3.41.0 takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Tag, Category, and Taxonomy Manager the fix is 3.42.0: builds <= 3.41.0 are affected, anything from 3.42.0 onward is not.

Remediation

Update to version 3.42.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Tag, Category, and Taxonomy Manager 3.42.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14371https://www.wordfence.com/threat-intel/vulnerabilities/id/1ef51ffb-df1e-442d-abc8-3a0308099a0bhttps://nvd.nist.gov/vuln/detail/CVE-2025-14371

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C