Custom Post Type UI <= 1.18.0 - Missing Authorization to Unauthenticated (Previously Administrator+) Custom Post Type Modification
Strategic Overview
- Status
- Patched in 1.18.1
- Affected Plugin
- Custom Post Type UI
- Affected Version
<= 1.18.0- CVSS
- 4.8Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12826
At a glance
CVE-2025-12826 is a medium-severity Missing Authorization vulnerability in the Custom Post Type UI WordPress plugin, affecting versions <= 1.18.0. It carries a CVSS score of 4.8 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 1.18.1; sites on affected versions should update now. Disclosed December 2025, reported by mahdi salhi (CaptinSharky01).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Custom Post Type UI <= 1.18.0 carries this weakness at cptui_process_post_type, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Custom Post Type UI the fix is 1.18.1: builds <= 1.18.0 are affected, anything from 1.18.1 onward is not.
Remediation
Update to version 1.18.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Custom Post Type UI 1.18.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C