HomeWordPress vulnerabilitiesCustom Post Types and Custom Fields creator
Custom Post Types and Custom Fields creator vulnerabilities
Custom Post Types and Custom Fields creator has 3 known vulnerabilities in this database. The most recent published record is dated 13 Nov 2026.
- Known vulnerabilities
- 3
- Active installs
- 10,000+
- Latest version
- 2.4.0
- Last updated
- 2 Nov 2026
- Most recent
- 13 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
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-2026-125783 | High 7.1 | Up to 2.4.0 | No fixed version yet | 9 d ago |
| Broken access control CVE-2026-125745 | Low 2.3 | Before 2.4.1 | Fixed in 2.4.1 | 12 d ago |
| Cross-site scripting (XSS) CVE-2022-4442 | Medium 4.8 | Before 2.3.3 | Fixed in 2.3.3 | 16 Jan 2023 |
Read the published descriptions
- CVE-2026-125783, 13 Nov 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in madalin.ungureanu Custom Post Types and Custom Fields creator - WCK wck-custom-fields-and-custom-post-types-creator allows Reflected XSS.This issue affects Custom Post Types and Custom Fields creator - WCK: from n/a through 2.4.0. CVE record
- CVE-2026-125745, 10 Nov 2026
- Custom Post Types and Custom Fields creator (WCK) before 2.4.1 contains a missing authorization vulnerability that allows authenticated attackers with access to any WCK meta box to read custom-field values on posts they cannot edit by exploiting the wck_show_update_form AJAX handler, which lacks the capability checks enforced by other handlers and relies on a shared, non-unique nonce action. Attackers can send a crafted admin-ajax.php request with a valid wck-edit-entry nonce, a target meta key, and an arbitrary post ID to disclose sensitive post-meta or option values belonging to other users, including private or draft post data. CVE record
- CVE-2022-4442, 16 Jan 2023
- The Custom Post Types and Custom Fields creator WordPress plugin before 2.3.3 does not sanitize and escape some of its settings, which could allow high-privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example, in multisite setup). CVE record
What to do if you run Custom Post Types and Custom Fields creator
If you run Custom Post Types and Custom Fields creator, 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 Types and Custom Fields creator vulnerabilities
Free. We email you when a new vulnerability is published for Custom Post Types and Custom Fields creator, 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.