CVE-2026-125745 · Package
NO FIX YET · SEE WHAT TO DO
The WCK plugin for WordPress before 2.4.1 has an AJAX handler that skips capability checks, so a logged-in user can read custom-field values on posts they cannot edit. An attacker can read private or draft post data and other users' sensitive post-meta or option values.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the WCK plugin before 2.4.1 where users with some account access can reach WCK meta boxes. The sources do not describe whether sites without public user registration are safe, so treat any site with logged-in contributors or subscribers as exposed.
Not affected if no-wck-meta-boxes, plugin-updated
Who cares self-hosted, wck, wordpress
wck_show_update_form AJAX action in the plugin code.2.4.1 or later.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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.