CVE-2026-119631: Kirki <= 6.4.1 - Missing Authorization to Unauthenticated Sensitive User Data Exposure via Editor-Preview-Token on AJAX 'get-dynamic-content-batch' / 'get-collection-batch'
The Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Unauthorized Data Access in versions up to, and including, 6.4.1 via the kirkipostapis AJAX action's get-dynamic-content-batch and get-collection-batch endpoints. This is due to the plugin opening these resolvers behind a site-wide, resource-unbound preview token (EditorPreview::hasvalidtoken()) that is NOT bound to the specific page the administrator intended to share, combined with the absence of any listusers or canuserreadpost() capability check inside HelperFunctions::getuserdynamiccontent() and Collection::getcollectionbatch() — the equivalent checks ARE present on the plugin's own REST route (FrontendRESTController::getitempermissionscheck()). This makes it possible for unauthenticated attackers holding any valid read-only share link to extract from the entire user table every user's useremail, firstname, lastname, nickname, registereddate, arbitrary string-valued usermeta (including custom keys such as billingphone), and the e-mail address of every approved commenter — information that WordPress itself withholds from anonymous readers (served only in the edit context behind listusers).
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Sites running Kirki version 6.4.1 or earlier are exposed if a valid read-only editor preview share link exists. An attacker does not need a WordPress account, but must possess any valid preview token from such a link.
Does the preview token limit access to the page that was shared?
No. The token is site-wide and is not bound to the specific page an administrator intended to share. A token from one shared preview can be used against the affected AJAX endpoints to request data beyond that page.
What information can be exposed?
The affected endpoints can expose all users' email addresses, names, nicknames, registration dates, and arbitrary string-valued user metadata, including custom fields such as billing_phone. They can also expose the email addresses of approved commenters.
How can I assess whether my site is affected?
Check whether Kirki is installed at version 6.4.1 or earlier and whether read-only editor preview links have been shared. The affected AJAX action is kirki_post_apis, using the get-dynamic-content-batch and get-collection-batch endpoints.