CVE-2026-84225

Kirki – Freeform Page Builder, Website Builder & Customizer 6.0.0 - 6.2.5 - Authenticated (Custom Role+) Insecure Direct Object Reference

2026-09-05 00:00
Revanth Meesala

Strategic Overview

Status
Patched in 6.3.0
Affected Plugin
Kirki – Freeform Page Builder, Website Builder & Customizer
Affected Version
6.0.0 – 6.2.5
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-84225
View all Kirki – Freeform Page Builder, Website Builder & Customizer vulnerabilities

At a glance

CVE-2026-84225 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Kirki WordPress plugin, affecting versions 6.0.0 – 6.2.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom Role level or above. The issue is fixed in version 6.3.0; sites on affected versions should update now. Disclosed September 2026, reported by Revanth Meesala.

Vulnerability Overview

The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions 6.0.0 through 6.2.5. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with custom role-level access and above, to perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Kirki 6.0.0 – 6.2.5 takes an account at Custom Role level or above. 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.3.0: builds 6.0.0 – 6.2.5 are affected, anything from 6.3.0 onward is not.

Remediation

Update to version 6.3.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.3.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-84225https://www.wordfence.com/threat-intel/vulnerabilities/id/3ceae1e5-49d6-4591-b756-594ac8e701ffhttps://nvd.nist.gov/vuln/detail/CVE-2026-84225

Related records

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