Custom Post Type UI Plugin up to 1.18.0 on WordPress cptui_process_post_type authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Custom Post Type UI Plugin up to 1.18.0 on WordPress. It has been declared as problematic. The impacted element is the function cptui_process_post_type. The manipulation results in authorization.
This vulnerability is reported as CVE-2025-12826. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in Custom Post Type UI Plugin up to 1.18.0 on WordPress. Affected is the function cptui_process_post_type. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity, and availability. CVE summarizes:
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.
The advisory is available at wordfence.com. This vulnerability is traded as CVE-2025-12826. The exploitability is told to be difficult. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 12/07/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at CNNVD (CNNVD-202512-590) and EUVD (EUVD-2025-201144). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.2
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.8
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/03/2025 Advisory disclosed12/03/2025 VulDB entry created
12/07/2025 VulDB entry last update
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2025-12826 (🔒)
GCVE (CVE): GCVE-0-2025-12826
GCVE (VulDB): GCVE-100-334242
EUVD: 🔒
CNNVD: CNNVD-202512-590 - WordPress plugin Custom Post Type UI 安全漏洞
Entry
Created: 12/03/2025 23:54Updated: 12/07/2025 15:12
Changes: 12/03/2025 23:54 (50), 12/04/2025 12:13 (1), 12/04/2025 12:29 (12), 12/05/2025 23:47 (6), 12/06/2025 18:55 (1), 12/07/2025 15:12 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.