GHSA-4C29-QRGF-VPXH
Vulnerability from github – Published: 2026-11-18 15:34 – Updated: 2026-11-18 15:34The 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).
{
"affected": [],
"aliases": [
"CVE-2026-119631"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T14:17:28Z",
"severity": "MODERATE"
},
"details": "The Kirki - Freeform Page Builder, Website Builder \u0026 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\u0027s `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()` \u2014 the equivalent checks ARE present on the plugin\u0027s 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\u0027s `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 \u2014 information that WordPress itself withholds from anonymous readers (served only in the `edit` context behind `list_users`).",
"id": "GHSA-4c29-qrgf-vpxh",
"modified": "2026-11-18T15:34:34Z",
"published": "2026-11-18T15:34:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119631"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax.php#L121"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax.php#L59"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/Collection.php#L147"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/DynamicContent.php#L103"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/DynamicContent.php#L135"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/HelperFunctions.php#L1100"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/HelperFunctions.php#L3368"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3793913/kirki/trunk/includes/HelperFunctions.php"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/kirki/#developers"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/60c1185d-3412-4b51-8bb7-8c6f79c5f580?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.