WordPress plugin · Updated daily · Source: Wordfence Intelligence

PublishPress Taxonomies vulnerabilities: affected versions and fixes

PublishPress Taxonomies has 40,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

PublishPress Taxonomies at a glance

  • 14 publicly disclosed vulnerabilities. The most recent was disclosed on Aug 19, 2026.
  • Ranked #813 by popularity on WordPress.org (40,000+ active installs).
  • The latest version is 4.0.2 (released Nov 17, 2026). The most recent security fix shipped in 3.52.0.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your PublishPress Taxonomies version

Enter the PublishPress Taxonomies version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “PublishPress Taxonomies”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “PublishPress Taxonomies”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (4.0.2). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known PublishPress Taxonomies vulnerabilities

  • Tag, Category, and Taxonomy Manager – Autotagger Automatically Add Terms <= 3.51.0 - Authenticated (Editor+) PHP Object Injection

    PHP object injection · CVE-2026-74012

    Affected versions: ≤ 3.51.0

    Fixed in: 3.52.0

    Severity: Medium 6.6 · Disclosed Aug 19, 2026

  • TaxoPress <= 3.50.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Private Post Disclosure

    Missing authorization · CVE-2026-15231

    Affected versions: ≤ 3.50.0

    Fixed in: 3.51.0

    Severity: Medium 4.3 · Disclosed Jul 24, 2026

  • TaxoPress <= 3.44.0 - Authenticated (Editor+) SQL Injection

    SQL injection · CVE-2026-42646

    Affected versions: ≤ 3.44.0

    Fixed in: 3.45.0

    Severity: Medium 4.9 · Disclosed Mar 22, 2026

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

    Missing authorization · CVE-2025-14371

    Affected versions: ≤ 3.41.0

    Fixed in: 3.42.0

    Severity: Medium 4.3 · Disclosed Jan 5, 2026

  • Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection via ORDER BY Clause

    SQL injection · CVE-2025-13922

    Affected versions: ≤ 3.40.1

    Fixed in: 3.41.0

    Severity: Medium 6.5 · Disclosed Dec 5, 2025

  • Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection

    SQL injection · CVE-2025-13359

    Affected versions: ≤ 3.40.1

    Fixed in: 3.41.0

    Severity: Medium 6.5 · Disclosed Dec 3, 2025

  • Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Taxonomy Term Manipulation

    Missing authorization · CVE-2025-13354

    Affected versions: ≤ 3.40.1

    Fixed in: 3.41.0

    Severity: Medium 4.3 · Disclosed Dec 3, 2025

  • Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.0 - Authenticated (Editor+) SQL Injection

    SQL injection · CVE-2025-11972

    Affected versions: ≤ 3.40.0

    Fixed in: 3.40.1

    Severity: Medium 4.9 · Disclosed Nov 7, 2025

  • Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.37.2 - Authenticated (Subscriber+) Information Exposure

    Information disclosure · CVE-2025-55710

    Affected versions: ≤ 3.37.2

    Fixed in: 3.37.3

    Severity: Medium 4.3 · Disclosed Aug 14, 2025

  • WordPress Tag, Category, and Taxonomy Manager – AI Autotagger <= 3.32.0 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-0627

    Affected versions: ≤ 3.32.0

    Fixed in: 3.33.0

    Severity: Medium 4.4 · Disclosed Apr 7, 2025

  • WordPress Tag and Category Manager – AI Autotagger <= 3.13.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2024-2830

    Affected versions: ≤ 3.12.0

    Fixed in: 3.20.0

    Severity: Medium 6.4 · Disclosed Apr 3, 2024

  • TaxoPress <= 3.6.4 - Authenticated (Editor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-2168

    Affected versions: ≤ 3.6.4

    Fixed in: 3.6.5

    Severity: Medium 5.5 · Disclosed Apr 18, 2023

  • TaxoPress <= 3.4.4 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 3.4.4

    Fixed in: 3.4.5

    Severity: Medium 6.1 · Disclosed Feb 7, 2022

  • TaxoPress <= 3.0.7.1 - Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24444

    Affected versions: ≤ 3.0.7.1

    Fixed in: 3.0.7.2

    Severity: Medium 5.5 · Disclosed Jun 30, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Aug 19, 2026.

Most common weaknesses in PublishPress Taxonomies

Cross-site scripting (XSS)

5 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

SQL injection

4 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Missing authorization

3 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is PublishPress Taxonomies safe to use?

PublishPress Taxonomies is a well-known plugin with 40,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.0.2) and turn on automatic updates.

How do I find which version of PublishPress Taxonomies my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesPublishPress Taxonomies on WordPress.org