Vulnerability in MB Custom Post Types & Custom Taxonomies (WordPress plugin) (CVE-2026-109982)
Summary
Vulnerability in MB Custom Post Types & Custom Taxonomies (WordPress plugin) (CVE-2026-109982). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-109982 has been found in MB Custom Post Types & Custom Taxonomies (WordPress plugin).
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MB Custom Post Types & Custom Taxonomies (WordPress plugin) CVE-2026-109982" on the vendor's site.
CVE-2026-109982 (MB Custom Post Types & Custom Taxonomies (WordPress plugin)) — CWE-862 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in MB Custom Post Types & Custom Taxonomies (WordPress plugin).
Check the vendor advisory for the affected versions of MB Custom Post Types & Custom Taxonomies (WordPress plugin).
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで MB Custom Post Types & Custom Taxonomies (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web wpscan.com
- web github.com
- web contact@wpscan.com