Skip to main content
Menu
CVEs

CVE

Kirki user data exposure in AJAX endpoints

CVE-2026-119631EUVD-2026-128843Published Updated

5.9MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

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).

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119631 (Kirki <= 6.4.1 - Missing Authorization to Unauthenticated Sensitive User Data Exposure via Editor-Preview-Token on AJAX…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119631 (entry last updated 2026-11-18):
Affected:
- themeum Kirki – Freeform Page Builder, Website Builder & Customizer: through 6.4.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119631 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/60c1185d-3412-4b51-8bb7-8c6f79c5f580?source=cve
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax.php#L121
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/HelperFunctions.php#L3368
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/DynamicContent.php#L135
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/HelperFunctions.php#L1100
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/DynamicContent.php#L103
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax.php#L59
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.4.1/includes/Ajax/Collection.php#L147
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119631
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119631"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • themeum Kirki – Freeform Page Builder, Website Builder & Customizer

    through 6.4.1

Evidence 12

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119631

Is CVE-2026-119631 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119631?

Kirki – Freeform Page Builder, Website Builder & Customizer: through 6.4.1.Source: cve.now feed data

More CVEs