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.
- Component
- MB Custom Post Types & Custom Taxonomies
- Plugin slug
mb-custom-post-types-custom-taxonomies- Affected
- 2.0.2 to < 2.12.3
- Safe version
2.12.3- Published
- Oct 22, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Oct 22, 2026 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
The authoritative export identifies 2.12.3 as fixed. Update to the applicable fixed release or a later supported release. Enforce server-side caller, object and operation permissions at the disclosed trust boundary; do not treat knowledge of identifiers or a nonce as authorization.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N