---
id: "CVE-2026-110010"
kind: "vulnerability"
aliases: ["CVE-2026-110010"]
title: "WordPress MB Custom Post Types plugin: unauthenticated request reverts post type settings"
severity: "medium"
cvss: 4.8
epss: 0.00168
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "wordpress", "wordpress-plugin"]
not_affected_if: ["already-updated", "fresh-install-2.0-or-later"]
published_at: "2026-10-22T06:17:13+00:00"
first_seen_at: "2026-10-23T21:57:30+00:00"
updated_at: "2026-10-25T04:33:05+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110010", "first_seen_at": "2026-10-23T21:57:30+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-110010", "first_seen_at": "2026-10-24T07:15:52+00:00"}]
---

# WordPress MB Custom Post Types plugin: unauthenticated request reverts post type settings

The MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.3 lets anyone without logging in re-run a legacy data migration. This rolls custom post type or taxonomy definitions back to their pre-upgrade state, discarding administrator changes and possibly exposing restricted content to anonymous visitors.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed plugin version in the WordPress admin plugins list or in `wp-content/plugins/` (look for the version in the plugin header) and see whether it is below `2.12.3`.
- Check whether the site was upgraded from a pre-2.0 release of the plugin, since the migration only applies to those sites.

## Fix

- Update the MB Custom Post Types & Custom Taxonomies plugin to `2.12.3` or later.

## Timeline

- 2026-10-23T21:57:30+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110010
- 2026-10-24T07:15:52+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-110010

## From the sources

The MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.3 does not perform any capability or authentication check before allowing an unauthenticated request to re-run a legacy data migration, letting anyone revert a custom post type or taxonomy definition on sites upgraded from a pre-2.0 release back to its pre-upgrade state. This discards configuration changes an administrator made after upgrading and, where those changes had restricted a definition's visibility, silently re-exposes the definition and its content to anonymous visitors.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_