WordPress security changelog
MEDIUM CVE-2026-13464 Deferred

Kirki frontend previews expose nonpublic posts without authentication

An unauthenticated POST to /wp-json/kirki/v1/frontend/collection can select context type post and an arbitrary numeric post ID, then use attacker-controlled kirki_data blocks to render the target's title, content and excerpt. Vulnerable releases expose drafts, pending, private, password-protected and trashed posts because the route does not enforce read_post permission for nonpublic targets.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Kirki – Freeform Page Builder, Website Builder & Customizer
Plugin slug
kirki
Affected
<= 6.0.14
Safe version
> 6.0.14
Published
Jul 24, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Jul 24, 2026 and is one of 17 known issues for this plugin.

What to do

Update, patch or deactivate.

The CNA lists versions through 6.0.14 as affected, so use a release newer than 6.0.14 until that range is corrected. Official 6.0.13 and 6.0.14 source already contain the relevant application fix: allow public posts, but require current_user_can('read_post', $post_id) for nonpublic targets. Backport that permission callback if upgrading is delayed.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

Primary and upstream sources