CVE-2026-110010

validatedZero produced an exploit or a check.

GHSA-95fw-7pmc-68c4 ↗EUVD-2026-108013 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
MB Custom Post Types & Custom Taxonomies >= 2.0.2, < 2.12.3
fixed in 2.12.3
ETK-2026-2400Zero's internal tracking ID, independent of the CVE number., permanent identifier
+48mTTV
26mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+48magent stopped
0
+10min
+20min
+30min
+40min

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

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-22 06:00Z
    cve_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.