{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-110011 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-110011 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110011 is a low-severity vulnerability in Unknown MB Custom Post Types \u0026 Custom Taxonomies, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-110011 and fix it if it is affected.\n\nWhat it is: CVE-2026-110011 is a low-severity vulnerability in Unknown MB Custom Post Types \u0026 Custom Taxonomies, published on 22 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-110011 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-110011/ (Markdown: https://insights.sbomify.com/CVE-2026-110011/index.md)","id":"CVE-2026-110011","markdown":"https://insights.sbomify.com/CVE-2026-110011/index.md","name":"CVE-2026-110011","record":{"aliases":["GHSA-r9xx-rhcx-ph2x"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The MB Custom Post Types \u0026 Custom Taxonomies WordPress plugin before 2.12.3 does not perform a capability check in its export feature, allowing users with a role as low as Contributor to read the configuration of admin-only custom post types and taxonomies, as well as the titles, dates, statuses and some stored content of other users' non-public posts and pages.","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":"The MB Custom Post Types \u0026 Custom Taxonomies WordPress plugin before 2.12.3 does not perform a capability check in its export feature, allow","id":"CVE-2026-110011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Salon Booking System \u003c 10.31.3 - Subscriber+ Booking PII Disclosure via REST bookings/upcoming","id":"CVE-2026-110012"},"packages":[],"prev":{"headline":"MB Custom Post Types \u0026 Custom Taxonomies 2.0.2 - 2.12.2 - Unauthenticated Settings Reset via 'mbcpt-force' Parameter","id":"CVE-2026-110010"},"products":["MB Custom Post Types \u0026 Custom Taxonomies"],"published":"2026-10-22","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-22","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-110011/"}