Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/obtain subscriber account
-
ExploitSend migration action request (no nonce)
-
ExecutionTrigger one-way migration
-
ImpactPublish records and permanently wipe CPT/taxonomy config
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account at any privilege level (subscriber or above, per PR:L) on a site running MB Custom Post Types & Custom Taxonomies before 2.12.2; in practice this means the target site must permit low-privilege/self-service user registration for an unprivileged outsider to exploit it. The vulnerable path is the plugin's migration action, which performs neither a capability check nor nonce validation, so no CSRF token or admin role is needed. Limiting factors: it is a one-way, single-shot migration (once triggered the configuration is already destroyed, so it cannot be repeated for further effect), there is no confidentiality exposure (C:N), and sites with registration disabled are only exposed to existing logged-in users. |
| Impact | This is a lower-tier but genuinely destructive broken-access-control flaw (CWE-862) rather than a high-urgency priority. The signals are internally consistent on the low-risk axis: the vendor CVSS base score is 4.2, EPSS is just 0.14% (3rd percentile) indicating no meaningful mass-exploitation pressure, it is NOT in CISA KEV, and no SSVC decision data was provided. The one aggravating signal is that publicly available exploit code exists (WPScan). However, exploitation is gated by PR:L - the attacker needs a valid authenticated account (e.g., subscriber), which limits opportunistic internet-wide abuse to sites that allow self-registration. Two signals conflict and should be verified: (1) the vendor vector sets AC:H, but the description (no capability check AND no nonce validation on the migration action) implies the trigger is trivial once authenticated, so I assess AC:L - the AC:H rating may reflect the one-way/single-shot nature of the migration rather than true exploit complexity; (2) the vendor rates availability impact A:L, yet the described effect is PERMANENT deletion of the entire post-type and taxonomy configuration, which is a severe, irreversible data-destruction outcome that arguably warrants A:H. Net: not a drop-everything issue by score or EPSS, but the destructive, non-reversible nature means any site permitting low-privilege user registration should patch promptly. |
| Exploit ScenarioDerived | On a WordPress site allowing open registration, an attacker signs up for a free subscriber account, then sends the plugin's migration action request directly (no nonce or capability check blocks it). The one-way migration fires, publishing new records and permanently wiping the site's entire custom post-type and taxonomy configuration - causing irreversible structural data loss. A public proof-of-concept is referenced by WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Missing authorization and CSRF protections in the MB Custom Post Types & Custom Taxonomies WordPress plugin before 2.12.2 allow any authenticated user - including a low-privileged subscriber - to trigger the plugin's one-way migration routine, which creates unwanted published records and permanently deletes the site's entire post-type and taxonomy configuration. The migration actions perform neither a capability check nor nonce validation (CWE-862 broken access control), so no administrator role or valid token is required; an independent assessment rates the availability impact as High because the configuration loss is irreversible. Publicly available exploit code exists (publicly available exploit code exists), but EPSS is low at 0.14% (3rd percentile) and there is no confirmed active exploitation; the primary practical prerequisite is that the target site accepts self-service/low-privilege registration.
RemediationAI
Vendor-released patch: upgrade MB Custom Post Types & Custom Taxonomies to version 2.12.2 or later, which is the first version outside the affected range (0 < 2.12.2); for most sites this means updating the plugin from the WordPress plugin repository or applying the vendor build, then confirming the version in the plugin list. If the plugin is not actively used, deactivating and deleting it removes the vulnerable migration handler entirely, which is the most reliable short-term mitigation at the cost of losing the post-type/taxonomy management functionality. Where immediate upgrading is not possible, restrict exposure by disabling open self-service registration and pruning existing subscriber/lower-privilege accounts so that an outsider cannot obtain the authenticated session the exploit requires - note this does not protect against legitimate but untrusted logged-in users and may break membership workflows. Because the vulnerable action lacks nonce validation, traditional CSRF hardening by the site owner is not a viable compensating control; a WAF rule blocking the plugin's migration action endpoint (unauthenticated or low-privilege callers) can reduce exposure but is bypassable and should be treated only as temporary. Before any migration is triggered, take a full database and configuration backup, since the configuration deletion is one-way and unrecoverable. Advisory reference: https://wpscan.com/vulnerability/27787d4e-1633-4eb6-bcf4-0a8586df3d47/.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a WordPress plugin that manages custom post types and custom taxonomies (the Meta Box 'MB Custom Post Types & Custom Taxonomies' family). Its migration handler - an action reachable by logged-in users through the plugin's admin-facing endpoints - implements neither a capability check (e.g. current_user_can) nor a nonce/referer validation (e.g. check_admin_referer or wp_verify_nonce). CWE-862 (Missing Authorization) is therefore the root-cause class: authorization is simply absent on a state-changing operation. Because the handler trusts any authenticated session, a subscriber-level account can reach it directly, and the migration is intentionally destructive and one-way, so the damage (deleted post-type/taxonomy definitions plus newly created published records) cannot be reversed by re-running the action. The CPE string cpe:2.3:a:unknown:mb_custom_post_types_&_custom_taxonomies records the vendor as unknown in the feed, but the affected product and version boundary are clear from the WPScan advisory and the ENISA EUVD entry (0 < 2.12.2).
Know when Mb Custom Post Types Custom Taxonomies gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
Any authenticated user can trivially trigger the unprotected action (PR:L, AC:L, UI:N); creation of records is I:L and permanent deletion of the entire configuration justifies A:H over the vendor's A:L.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-102690
GHSA-45hq-3vxw-q94x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB