Custom Post Type UI <= 1.18.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'label' Import Parameter
Strategic Overview
- Status
- Patched in 1.18.2
- Affected Plugin
- Custom Post Type UI
- Affected Version
<= 1.18.1- CVSS
- 4.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2025-14056
At a glance
CVE-2025-14056 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Custom Post Type UI WordPress plugin, affecting versions <= 1.18.1. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.18.2; sites on affected versions should update now. Disclosed December 2025, reported by type5afe.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Custom Post Type UI <= 1.18.1 carries this weakness at label, and reaching it takes an account at Administrator level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Custom Post Type UI the fix is 1.18.2: builds <= 1.18.1 are affected, anything from 1.18.2 onward is not.
Remediation
Update to version 1.18.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Custom Post Type UI 1.18.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C