HomeWordPress vulnerabilitiesCustom Post Type UI
Custom Post Type UI vulnerabilities
Custom Post Type UI has 3 known vulnerabilities in this database. The most recent published record is dated 13 Dec 2025.
- Known vulnerabilities
- 3
- Active installs
- 1m+
- Latest version
- 1.19.3
- Last updated
- 14 Jul 2026
- Most recent
- 13 Dec 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2025-14056 | Medium 4.4 | Up to 1.18.1 | Fixed in a later version (latest 1.19.3) | 13 Dec 2025 |
| Broken access control CVE-2025-12826 | Medium 4.8 | Up to 1.18.0 | Fixed in a later version (latest 1.19.3) | 4 Dec 2025 |
| Cross-site request forgery (CSRF) CVE-2023-1623 | Medium 6.5 | Before 1.13.5 | Fixed in 1.13.5 | 24 Apr 2023 |
Read the published descriptions
- CVE-2025-14056, 13 Dec 2025
- The Custom Post Type UI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'label' parameter during custom post type import in all versions up to, and including, 1.18.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses the Tools → Get Code page. CVE record
- CVE-2025-12826, 4 Dec 2025
- 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 record
- CVE-2023-1623, 24 Apr 2023
- The Custom Post Type UI WordPress plugin before 1.13.5 does not properly check for CSRF when sending the debug information to a user supplied email, which could allow attackers to make a logged in admin send such information to an arbitrary email address via a CSRF attack. CVE record
What to do if you run Custom Post Type UI
If you run Custom Post Type UI, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Custom Post Type UI vulnerabilities
Free. We email you when a new vulnerability is published for Custom Post Type UI, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.