CVE-2026-15286

Gutenberg Blocks with AI by Kadence WP – Page Builder Features <= 3.5.32 - Incorrect Authorization to Authenticated (Contributor+) Post Publication

2026-02-10 00:00
johska

Strategic Overview

Status
Patched in 3.6.0
Affected Plugin
Kadence Blocks — Page Builder Toolkit for Gutenberg Editor
Affected Version
<= 3.5.32
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-15286
View all Kadence Blocks — Page Builder Toolkit for Gutenberg Editor vulnerabilities

At a glance

CVE-2026-15286 is a medium-severity Incorrect Authorization vulnerability in the Kadence Blocks WordPress plugin, affecting versions <= 3.5.32. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.6.0; sites on affected versions should update now. Disclosed February 2026, reported by johska.

Vulnerability Overview

The Gutenberg Blocks with AI by Kadence WP – Page Builder Features plugin for WordPress is vulnerable to unauthorized post publication in all versions up to, and including, 3.5.32 due to a misconfigured capability check on the 'get_items_permission_check' function permission callback of the 'process_pattern' REST API endpoint. This makes it possible for authenticated attackers, with Contributor-level access and above, to create and immediately publish posts of any type (including pages), bypassing the standard WordPress review workflow where contributors must submit posts for administrator approval.

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-863: Incorrect Authorization

Kadence Blocks <= 3.5.32 carries this weakness at get_items_permission_check, and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Kadence Blocks the fix is 3.6.0: builds <= 3.5.32 are affected, anything from 3.6.0 onward is not.

Remediation

Update to version 3.6.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: Kadence Blocks 3.6.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-15286https://www.wordfence.com/threat-intel/vulnerabilities/id/6e739eb4-6b8b-4bc7-a1e6-790180668c93https://nvd.nist.gov/vuln/detail/CVE-2026-15286

Related records

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