# Custom Post Types and Custom Fields creator – WCK <= 2.4.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Map Marker Values

- **ID:** WPSEC-2026-2997
- **Plugin:** Custom Post Types and Custom Fields creator – WCK (`wck-custom-fields-and-custom-post-types-creator`), https://wordpress.org/plugins/wck-custom-fields-and-custom-post-types-creator/
- **Affected versions:** from 1.2.9 before 2.4.1
- **Fixed in:** 2.4.1 (Update to 2.4.1 or later.)
- **Severity:** Medium 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)
- **Weakness:** CWE-79
- **Usage among sites WPSec scans:** plugin Low, affected versions Low (as of 2026-11-12)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/wck-custom-fields-and-custom-post-types-creator
- **Fix released:** 2026-11-10
- **Published:** 2026-11-12
- **URL:** https://wpsec.com/vuln/WPSEC-2026-2997/

## Description

The WCK plugin for WordPress is vulnerable to Stored Cross-Site Scripting via map field marker values in all versions up to, and including, 2.4.0, due to insufficient input validation and missing output escaping when markers are printed into the value attribute of the map field's hidden inputs. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary attributes, and through them web scripts, into the editor screen that renders the map field. The scripts run when a user who opens that screen interacts with the injected element.

## References

- https://wpsec.com/vuln/WPSEC-2026-2997/
- https://plugins.svn.wordpress.org/wck-custom-fields-and-custom-post-types-creator/tags/2.4.1/
- https://wordpress.org/plugins/wck-custom-fields-and-custom-post-types-creator/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-2997/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.