Custom Post Type UI: A security weakness
Custom Post Type UI is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Custom Post Type UI
- Plugin slug
custom-post-type-ui- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Dec 04, 2025
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Dec 04, 2025 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update Custom Post Type UI to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Custom Post Type UI plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.18.0. This is due to the plugin not verifying that a user has the required capability to perform actions in the "cptui_process_post_type" function. This makes it possible for authenticated attackers, with subscriber level access and above, to add, edit, or delete custom post types in limited situations.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L