Custom Post Type UI vulnerability records, and where to read its post type settings
Custom Post Type UI saves the settings that register a site's custom post types and taxonomies.
Where to read each type's "Public", "Show in REST API" and "Capability Type" values, which no version number reveals, and how its records' fields read.
On this page
Custom Post Type UI vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 4 records for Custom Post Type UI. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 1.18.2
Worked out from data retrieved on .
Every affected range listed in this source for Custom Post Type UI ends before version 1.18.2.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Custom Post Type UI <= 1.18.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'label' Import Parameter
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2025-14056
Affected versions- All versions up to and including 1.18.1
Patched versions: 1.18.2
Update to at least version 1.18.2.
Custom Post Type UI <= 1.18.0 - Missing Authorization to Unauthenticated (Previously Administrator+) Custom Post Type Modification
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.8)
- CVE:
- CVE-2025-12826
Affected versions- All versions up to and including 1.18.0
Patched versions: 1.18.1
Update to at least version 1.18.1.
Custom Post Type UI <= 1.13.4 - Cross-Site Request Forgery to Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2023-1623
Affected versions- All versions up to and including 1.13.4
Patched versions: 1.13.5
Update to at least version 1.13.5.
Custom Post Type UI <= 1.7.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
Affected versions- All versions before 1.7.4
Patched versions: 1.7.4
Update to at least version 1.7.4.
Check Custom Post Type UI on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Custom Post Type UI registers and where it takes input
The WordPress.org listing for Custom Post Type UI carries the byline "By webdevstudios".
It describes an interface for registering and managing custom post types and taxonomies with no coding required, and says "CPTUI handles registration. CPT UI Pro handles everything else."
Those registration settings are the plugin's input. The plugin's help text describes settings such as "Public" and "Show in REST API" for each type, and a "Capability Type" for each post type. The vendor's articles place editing in "Add/Edit Post Types" and "Add/Edit Taxonomies" areas, and describe an Import/Export page where the settings for all post types and taxonomies are copied out as text or pasted in from another site.
What the Custom Post Type UI records show
Cross-Site Request Forgery and Stored Cross-Site Scripting each appear in more than one of the titles named here.
Two of those titles carry access wording, quoted as written, and two carry none.
- CVE-2025-14056, published 12 Dec 2025, has a title ending "Authenticated (Administrator+) Stored Cross-Site Scripting via 'label' Import Parameter". Affected: all versions up to and including 1.18.1. Patched versions: 1.18.2.
- CVE-2025-12826, published 3 Dec 2025, has a title ending "Unauthenticated (Previously Administrator+) Custom Post Type Modification". Affected: all versions up to and including 1.18.0. Patched versions: 1.18.1.
- CVE-2023-1623 has a title ending "Cross-Site Request Forgery to Sensitive Information Exposure". Affected: all versions up to and including 1.13.4. Patched versions: 1.13.5.
- A record with no CVE id, published 18 Mar 2020, has a title ending "Cross-Site Request Forgery to Stored Cross-Site Scripting" and a severity of High (CVSS 8.8) in the history. Affected: all versions before 1.7.4. Patched versions: 1.7.4.
Reading the version fields
CVE-2025-12826 lists 1.18.1 in its patched versions field, and the affected range of CVE-2025-14056 runs up to and including 1.18.1, so a copy on 1.18.1 is outside the first record and inside the second. Read each record's affected range and patched versions field against your installed version.
The 2020 record has a title beginning "Custom Post Type UI <= 1.7.3", while its affected range reads all versions before 1.7.4. Match on the fields, not the title.
Where to read each Custom Post Type UI check
For each item in the checklist on this page, use an account that can open the "CPTUI" menu the listing's installation steps name, on a site you are authorised to review, and only read and copy.
The vendor's slug article describes a rename as entering a new slug, checking a checkbox to migrate the posts or terms and clicking "Save Post Type" or "Save Taxonomy". Leave each edit screen without pressing either.
Record the version number in the Description column of the Custom Post Type UI row on the Plugins screen, the day you read it, and any update notice WordPress shows for that row. The changelog on the plugin's WordPress.org listing, where some lines mark security fixes, such as "Fixed: Security issue around Get Code functionality.", is a second place to read before an update.
If the Plugins screen also lists CPT UI Pro, record its version on a line of its own.
The listing's screenshot captions include "Registered post types and taxonomies from CPTUI", and one of the plugin's own labels reads "Registered types & taxonomies". Write down every post type and taxonomy listed, with its slug.
Then open each from the "Edit Post Types" or "Edit Taxonomies" tab the slug article names, and record "Public". The help text describes it for a post type as "Whether or not posts of this type should be shown in the admin UI and is publicly queryable", and for a taxonomy as "Whether a taxonomy is intended for use publicly either via the admin interface or by front-end users."
Vendor pages name this screen two ways. The migration article calls it the Import/Export page, with a Taxonomies tab, and the debug info article the Import/Export section, where it finds a "Debug info" tab, while the listing's captions name a "Tools screen" and the plugin's menu labels include "Tools".
The migration article puts the export text in the right textarea and the import box on the left. Copy both exports as a dated record of every type's settings, leave the import box empty, and leave the email field on the debug info tab blank.
For each post type and taxonomy, record "Show in REST API", which the help text describes as whether to show the type's data in the WP REST API, and "REST API base slug", the "Slug to use in REST API URLs".
Record "REST API namespace" and "REST API controller class" as well, mark any value other than the default the help text gives, and ask the developer what it is for.
Do not assume the first field's default. The vendor's REST API article, last updated on 12 Dec 2022, says it "defaults to false", while the help text in the plugin's files reads "(Custom Post Type UI default: true)". Then, as a check of your own while signed out, request /wp-json/ followed by the namespace and base slug you recorded, and note the status code and whether entries come back.
Record each post type's "Capability Type", whose help text reads "The post type to use for checking read, edit, and delete capabilities." Set each value beside the people in each role, using the role filter links on the Users screen. WordPress's roles documentation says an Editor can publish and manage posts including the posts of other users.
Then look for add-ons and code. The plugin's help text recommends Custom Post Type UI Capabilities on GitHub for the addition of extra fields regarding roles and capabilities. Note whether it is installed. Among the plugin's filters, the vendor's hooks page, which says it is current as of version 1.12.0 and calls itself a work in progress, names cptui_required_capabilities and cptui_map_meta_cap. Search the theme and site plugins for both and record each match for the developer to explain.
Type settings that a Custom Post Type UI version leaves open
Custom Post Type UI's version number places the installed copy inside or outside each affected range.
It says nothing about whether the site has been attacked, or about how the types the plugin registers are set up: a type left public or shown in the REST API without anyone deciding it should be, a capability type nobody chose, a non-default REST controller class, or settings imported from another site.
A WordPress security audit tests what those settings let through: it requests each REST route under /wp-json/ with no session, and with its contributor and author test accounts it tries to publish, schedule or edit another user's post in the editor and through the REST API.
Frequently asked questions
The plugin's help text says renaming the slug for a post type or taxonomy "creates a new entry in our saved option which gets registered as its own post type or taxonomy", with the settings mirrored from the previous slug. Record both entries and their slugs. The help text's next step, deleting the previous entry, changes the site, so it is not part of a read-only review.
The records on this page are those the source data files under the custom-post-type-ui slug, and being filed there does not settle whether a record also applies to CPT UI Pro. The vendor's pages differ on whether Pro needs the free plugin installed. The listing's FAQ says "CPT UI Pro does not require Custom Post Type UI (free)", while the plugin's own help text, asked whether Custom Post Type UI is still needed with Pro, answers "Yes you will" and says Pro "is not a replacement of the free version".
No. The plugin's help text says it "will not export the associated posts or taxonomy terms, just the settings", and warns of the import side that "Importing will overwrite previous registered settings."
The vendor's article says entering an email address and clicking "Send debug info" sends the data to that address. It lists the data as including multisite status, URLs for the website, the WordPress version, active theme, registered post types, server information, active and inactive plugins, and the plugin's own post type and taxonomy data.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 3 of the 4 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Custom Post Type UI <= 1.18.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'label' Import Parameter (CVE-2025-14056)
- Custom Post Type UI <= 1.18.0 - Missing Authorization to Unauthenticated (Previously Administrator+) Custom Post Type Modification (CVE-2025-12826)
- Custom Post Type UI <= 1.13.4 - Cross-Site Request Forgery to Sensitive Information Exposure (CVE-2023-1623)
- Custom Post Type UI <= 1.7.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting