# CVE-2026-110010: MB Custom Post Types & Custom Taxonomies 2.0.2 - 2.12.2 - Unauthenticated Settings Reset via 'mbcpt-force' Parameter


- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-95fw-7pmc-68c4

## What is CVE-2026-110010?

CVE-2026-110010 is a medium-severity vulnerability in Unknown MB Custom Post Types & Custom Taxonomies, published on 22 Oct 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-110010?


## How do I fix CVE-2026-110010?

No fix has been published for CVE-2026-110010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110010 being exploited?

There is no known exploitation of CVE-2026-110010 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110010 and fix it if it is affected.

What it is: CVE-2026-110010 is a medium-severity vulnerability in Unknown MB Custom Post Types & Custom Taxonomies, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110010 in the wild and no public exploit code.

Affected product: Unknown MB Custom Post Types & Custom Taxonomies. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110010/ (Markdown: https://insights.sbomify.com/CVE-2026-110010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110010
- OSV: https://osv.dev/vulnerability/CVE-2026-110010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110010/
Summaries are generated and may contain mistakes; the official description above is the record.