CVE-2026-18347

Kirki <= 6.1.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via 'context' Parameter

2026-08-15 17:56
Datist Pham

Strategic Overview

Status
Patched in 6.2.0
Affected Plugin
Kirki – Freeform Page Builder, Website Builder & Customizer
Affected Version
<= 6.1.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-18347
View all Kirki – Freeform Page Builder, Website Builder & Customizer vulnerabilities

At a glance

CVE-2026-18347 is a medium-severity Missing Authorization vulnerability in the Kirki WordPress plugin, affecting versions <= 6.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.2.0; sites on affected versions should update now. Disclosed August 2026, reported by Datist Pham.

Vulnerability Overview

The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.1.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to read arbitrary user metadata and sensitive user record fields — including email address, assigned roles, registration date, and any user_meta values — belonging to any WordPress user including administrators, by supplying a target user ID with a user-type context to the frontend collection endpoint.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Kirki <= 6.1.1 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Kirki the fix is 6.2.0: builds <= 6.1.1 are affected, anything from 6.2.0 onward is not.

Remediation

Update to version 6.2.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Kirki 6.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-18347https://www.wordfence.com/threat-intel/vulnerabilities/id/fa1e0bcd-f881-4b01-b802-7cb18a22a07fhttps://nvd.nist.gov/vuln/detail/CVE-2026-18347

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C