← WordPress Vulnerabilities
WordPress security by component

MB Custom Post Types & Custom Taxonomies

MB Custom Post Types & Custom Taxonomies creates and manages custom post types and custom taxonomies in WordPress.

MB Custom Post Types & Custom Taxonomies (mb-custom-post-types-custom-taxonomies) is a WordPress plugin with 4 published CVE records in this archive. The latest tracked vulnerability was published Oct 22, 2026; the highest published CVSS base score is 4.8.

Plugin slug: mb-custom-post-types-custom-taxonomies

CVE-2026-110011: MB Custom Post Types & Custom Taxonomies: Unauthorized export of private post information

The MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.3 does not perform a capability check in its export feature, allowing users with a role as low as Contributor to read the configuration of admin-only custom post types and taxonomies, as well as the titles, dates, statuses and some stored content of other users' non-public posts and pages. Other endpoint, parameter, role or implementation details not named in this export are not established by this record. Affected versions: 2.4.0 to before 2.12.3. The narrative names the role described above, while the CVSS vector records high privileges (PR:H); that vector does not establish an Administrator-only requirement.

PublishedOct 22, 2026
Known safe version2.12.3
Known source slugs: mb-custom-post-types-&-custom-taxonomies, mb-custom-post-types-custom-taxonomies
Published vulnerabilities for mb-custom-post-types-custom-taxonomies
Safe version
Oct 22, 2026 CVE-2026-110011
MB Custom Post Types & Custom Taxonomies: Unauthorized export of private post information
The MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.3 does not perform a capability check in its export feature, allowing users with a role as low as Contributor to read the configuration of admin-only custom post types and taxonomies, as well as the titles, dates, statuses and some stored content of other users' non-public posts and pages. Other endpoint, parameter, role or implementation details not named in this export are not established by this record. Affected versions: 2.4.0 to before 2.12.3. The narrative names the role described above, while the CVSS vector records high privileges (PR:H); that vector does not establish an Administrator-only requirement.
2.12.3
CVE2.7
Oct 22, 2026 CVE-2026-110010
MB Custom Post Types & Custom Taxonomies: Unauthenticated replay of legacy configuration migration
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. Other endpoint, parameter, role or implementation details not named in this export are not established by this record. Affected versions: 2.0.2 to before 2.12.3.
2.12.3
CVE4.8
Oct 16, 2026 CVE-2026-109982
MB Custom Post Types & Custom Taxonomies: Missing authorization
The MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.2 does not perform a capability check or validate a nonce on its migration actions, allowing any authenticated user, such as a subscriber, to trigger a one-way migration that creates published records and permanently deletes a companion MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.2's entire post-type and taxonomy configuration. The export supplies no additional endpoint, action, parameter or function details beyond those described above.
2.12.2
CVE4.2
May 15, 2025 CVE-2024-10143
MB Custom Post Types & Custom Taxonomies: Cross-site scripting
MB Custom Post Types & Custom Taxonomies is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE4.8