CVE-2026-110010
validatedZero produced an exploit or a check.GHSA-95fw-7pmc-68c4 ↗EUVD-2026-108013 ↗
description
MB Custom Post Types & Custom Taxonomies before 2.12.3 can allow unauthenticated requests to rerun an older migration process. On sites upgraded from a pre-2.0 release, this can restore prior post type or taxonomy settings, remove later administrator changes, and potentially expose previously restricted content.
mitigation
Update MB Custom Post Types & Custom Taxonomies to version 2.12.3 or later. Until updated, restrict access to the affected WordPress site and review definitions whose visibility was changed after upgrading from a pre-2.0 release.
fixed in 2.12.3
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-22 06:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-110010
{ "etk_id": "ETK-2026-2400", "cve_id": "CVE-2026-110010", "display_id": "CVE-2026-110010", "ghsa_id": "GHSA-95fw-7pmc-68c4", "euvd_id": "EUVD-2026-108013", "status": "published", "anchor_state": "anchored", "title": "Unauthenticated migration rollback in MB Custom Post Types", "summary": "MB Custom Post Types & Custom Taxonomies before 2.12.3 can allow unauthenticated requests to rerun an older migration process. On sites upgraded from a pre-2.0 release, this can restore prior post type or taxonomy settings, remove later administrator changes, and potentially expose previously restricted content.", "mitigation": "Update MB Custom Post Types & Custom Taxonomies to version 2.12.3 or later. Until updated, restrict access to the affected WordPress site and review definitions whose visibility was changed after upgrading from a pre-2.0 release.", "vendor": null, "product": "MB Custom Post Types & Custom Taxonomies", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 2.0.2, < 2.12.3" ], "ecosystem": null, "fixed_versions": [ "2.12.3" ], "package_name": "MB Custom Post Types & Custom Taxonomies", "purl": null } ], "cwes": null, "cvss_score": null, "cvss_src": null, "cvss_vector": null, "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 25.52669385, "t0_at": "2026-10-22T06:00:17.601000+00:00", "signals": { "check": { "at": "2026-10-22T06:48:35.478108+00:00", "days": 0.03354024430555556, "is_lower_bound": false, "measured_at": "2026-10-22T06:00:17.601000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-22T06:00:17.601000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-22T06:00:17.601000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-110010" } } }
published 2026-10-22 06:23Z
last change 2026-10-22 08:18Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.