CVE-2026-11357

Kadence Blocks <= 3.7.5 - Authenticated (Contributor+) Sensitive Information Exposure via Block Editor proData Localization

2026-06-17 16:14
se1en

Strategic Overview

Status
Patched in 3.7.6
Affected Version
<= 3.7.5
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-11357
View all Kadence Blocks — Page Builder Toolkit for Gutenberg Editor vulnerabilities

At a glance

CVE-2026-11357 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Kadence Blocks WordPress plugin, affecting versions <= 3.7.5. 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.7.6; sites on affected versions should update now. Disclosed June 2026, reported by se1en.

Vulnerability Overview

The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.7.5 via the editor_assets_variables. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the site's connected Kadence account license key, license owner email, api_key, api_email, and license domain from the browser console by inspecting window.kadence_blocks_params.proData. Exploitation requires only that an administrator has previously connected a valid Kadence license; the full credential bundle is then readable by any Contributor-level user from the block editor client context without any server-side request manipulation.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Kadence Blocks <= 3.7.5 takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Kadence Blocks the fix is 3.7.6: builds <= 3.7.5 are affected, anything from 3.7.6 onward is not.

Remediation

Update to version 3.7.6, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Kadence Blocks 3.7.6 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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