CVE-2026-110010 MB Custom Post Types & Custom Taxonomies CVE debrief

Who should care

Administrators of WordPress sites using the MB Custom Post Types & Custom Taxonomies plugin should assess their exposure and take necessary actions to prevent unauthorized settings resets.

Why it matters

The CVE-2026-110010 vulnerability in the MB Custom Post Types & Custom Taxonomies WordPress plugin allows an unauthenticated attacker to reset settings to their pre-upgrade state, potentially re-exposing restricted content. Site administrators should verify their site's exposure, update to version 2.12.3 or later, and review affected definitions.

• An attacker could revert custom post type or taxonomy definitions to their pre-upgrade state, potentially re-exposing restricted content to anonymous visitors.
• Site administrators may need to review and restore affected definitions to prevent unintended changes.
• The vulnerability could lead to unintended changes in site configurations and content.

Technical summary

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. This lets anyone revert a custom post type or taxonomy definition on sites upgraded from a pre-2.0 release back to its pre-upgrade state, potentially re-exposing restricted content to anonymous visitors. Site administrators should verify their site's exposure and update to version 2.12.3 or later. They should also review and restore any affected custom post type or taxonomy definitions to prevent unintended changes.

Defensive priority

Administrators of WordPress sites using the MB Custom Post Types & Custom Taxonomies plugin should verify their site's exposure and update to version 2.12.3 or later. They should also review and restore any affected custom post type or taxonomy definitions.

Recommended defensive actions

• Verify the version of the MB Custom Post Types & Custom Taxonomies plugin and update to 2.12.3 or later if necessary.
• Review and restore any affected custom post type or taxonomy definitions.
• Monitor site configurations and content for unauthorized changes.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details about the vulnerability, but the impact and affected versions require verification from official sources. The vendor's canonical source is listed as 'reference_domain_weak' with low confidence.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.