Kirki <= 6.3.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Exposure via Context Smuggling via 'context' Parameter
Strategic Overview
- Status
- Patched in 6.4.0
- Affected Plugin
- Kirki – Freeform Page Builder, Website Builder & Customizer
- Affected Version
<= 6.3.2- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-107762
At a glance
CVE-2026-107762 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Kirki WordPress plugin, affecting versions <= 6.3.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 6.4.0; sites on affected versions should update now. Disclosed October 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.3.2 via the 'context' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to expose arbitrary users' sensitive profile data — including email address, display name, nicename, registration date, profile image URL, and any string-valued user meta fields such as first name, last name, nickname, description, and custom meta keys — via the REST response. Exploitation requires a published page that uses a Kirki template containing at least one user-type dynamic content block; target user IDs are enumerable via standard WordPress REST endpoints, making the only prerequisite the presence of such a template on the site.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
Kirki <= 6.3.2 carries this weakness at context, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Kirki the fix is 6.4.0: builds <= 6.3.2 are affected, anything from 6.4.0 onward is not.
Remediation
Update to version 6.4.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Kirki 6.4.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Kirki – Freeform Page Builder, Website Builder & Customizer
- 9.8CVE-2026-103065: Kirki RCE
CVE-2026-103065 - 9.8CVE-2026-16747: Kirki RCE
CVE-2026-16747 - 9.8CVE-2026-8206: Kirki 6.0.0 - 6.0.6 Privilege Escalation
CVE-2026-8206 - 8.1CVE-2026-12720: Kirki PHP Object Injection
CVE-2026-12720 - 8.1CVE-2026-57724: Kirki PHP Object Injection
CVE-2026-57724 - 7.5CVE-2026-12721: Kirki <= 6.0.12 SQL Injection
CVE-2026-12721 - 7.5CVE-2026-57726: Kirki SQL Injection
CVE-2026-57726 - 7.5CVE-2026-8073: Kirki <= 6.0.6 Limited Arbitrary File Read and Deletion
CVE-2026-8073
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C