CVE-2026-110011

MB Custom Post Types & Custom Taxonomies 2.4.0 - 2.12.2 - Missing Authorization

2026-10-20 00:00
RIA Labs

Strategic Overview

Status
Patched in 2.12.3
Affected Version
2.4.0 – 2.12.2
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-110011
View all MB Custom Post Types & Custom Taxonomies vulnerabilities

At a glance

CVE-2026-110011 is a medium-severity Incorrect Authorization vulnerability in the MB Custom Post Types & Custom Taxonomies WordPress plugin, affecting versions 2.4.0 – 2.12.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.12.3; sites on affected versions should update now. Disclosed October 2026, reported by RIA Labs.

Vulnerability Overview

The MB Custom Post Types & Custom Taxonomies plugin for WordPress is vulnerable to unauthorized access in versions 2.4.0 through 2.12.2. This is due to a missing capability check on a function. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

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-863: Incorrect Authorization

Reaching this weakness in MB Custom Post Types & Custom Taxonomies 2.4.0 – 2.12.2 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For MB Custom Post Types & Custom Taxonomies the fix is 2.12.3: builds 2.4.0 – 2.12.2 are affected, anything from 2.12.3 onward is not.

Remediation

Update to version 2.12.3, 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: MB Custom Post Types & Custom Taxonomies 2.12.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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