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'
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| themeum | Kirki – Freeform Page Builder, Website Builder & Customizer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Themeum | Kirki |
|
||||||||
| Wordpress-extensions | Kirki |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Themeum
Themeum kirki Wordpress-extensions Wordpress-extensions kirki |
|
| Vendors & Products |
Themeum
Themeum kirki Wordpress-extensions Wordpress-extensions kirki |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 `kirki_post_apis` 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::has_valid_token()`) that is NOT bound to the specific page the administrator intended to share, combined with the absence of any `list_users` or `can_user_read_post()` capability check inside `HelperFunctions::get_user_dynamic_content()` and `Collection::get_collection_batch()` — the equivalent checks ARE present on the plugin's own REST route (`FrontendRESTController::get_item_permissions_check()`). This makes it possible for unauthenticated attackers holding any valid read-only share link to extract from the entire user table every user's `user_email`, `first_name`, `last_name`, `nickname`, `registered_date`, arbitrary string-valued `user_meta` (including custom keys such as `billing_phone`), and the e-mail address of every approved commenter — information that WordPress itself withholds from anonymous readers (served only in the `edit` context behind `list_users`). | |
| Title | 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' | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV3_1
|