CVE-2026-13464

Kirki <= 6.0.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'context' Parameter

2026-07-23 14:28
Abu Hurayra (HurayraIIT)

Strategic Overview

Status
Patched in 6.1.0
Affected Plugin
Kirki – Freeform Page Builder, Website Builder & Customizer
Affected Version
<= 6.0.14
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-13464
View all Kirki – Freeform Page Builder, Website Builder & Customizer vulnerabilities

At a glance

CVE-2026-13464 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Kirki WordPress plugin, affecting versions <= 6.0.14. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.0; sites on affected versions should update now. Disclosed July 2026, reported by Abu Hurayra (HurayraIIT).

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.0.14 via the 'context' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to read the full title, content, and excerpt of any WordPress post — including drafts, pending, privately published, password-protected, and trashed posts — regardless of author, by supplying an arbitrary post ID via the context parameter alongside an attacker-controlled block template.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Kirki <= 6.0.14 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.1.0: builds <= 6.0.14 are affected, anything from 6.1.0 onward is not.

Remediation

Update to version 6.1.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.1.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-13464https://www.wordfence.com/threat-intel/vulnerabilities/id/84f65255-f710-44f9-9f77-61776a40abaehttps://nvd.nist.gov/vuln/detail/CVE-2026-13464

Related records

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