{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-109982 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-109982 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-109982 is a medium-severity missing authorization vulnerability in Unknown MB Custom Post Types \u0026 Custom Taxonomies, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-109982 and fix it if it is affected.\n\nWhat it is: CVE-2026-109982 is a medium-severity missing authorization vulnerability in Unknown MB Custom Post Types \u0026 Custom Taxonomies, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-109982 in the wild and no public exploit code.\n\nAffected product: Unknown MB Custom Post Types \u0026 Custom Taxonomies. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-109982/ (Markdown: https://insights.sbomify.com/CVE-2026-109982/index.md)","id":"CVE-2026-109982","markdown":"https://insights.sbomify.com/CVE-2026-109982/index.md","name":"CVE-2026-109982","record":{"aliases":["GHSA-45hq-3vxw-q94x"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can trigger unauthorized migration actions, permanently deleting post-type configurations and creating published records.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The MB Custom Post Types \u0026 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 \u0026 Custom Taxonomies WordPress plugin before 2.12.2's entire post-type and taxonomy configuration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MB Custom Post Types \u0026 Custom Taxonomies \u003c 2.12.2 - Subscriber+ Missing Authorization via CPT UI Migration","id":"CVE-2026-109982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"YMC Filter \u003c= 3.12.19 - Authenticated (Author+) Stored DOM-Based Cross-Site Scripting via 'post_title' Parameter","id":"CVE-2026-109983"},"packages":[],"prev":{"headline":"The Related Posts for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3","id":"CVE-2026-109980"},"products":["MB Custom Post Types \u0026 Custom Taxonomies"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Unknown"]},"summary":"Authenticated subscribers can trigger unauthorized migration actions, permanently deleting post-type configurations and creating published records.","url":"https://insights.sbomify.com/CVE-2026-109982/"}