WordPress security changelog
MEDIUM CVE-2026-18062 Received

Kadence Identity image content lets Contributors store JavaScript

Kadence Blocks through 3.7.8.1 insufficiently sanitizes and escapes Identity block inner-image content in build_html(). A Contributor can store JavaScript that executes for page viewers when urlTransparent is non-empty; the record does not disclose the exact image field or payload encoding.

CVE / CNA score 6.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Kadence Blocks — Page Builder Toolkit for Gutenberg Editor
Plugin slug
kadence-blocks
Affected
<= 3.7.8.1
Safe version
> 3.7.8.1
Published
Aug 01, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Aug 01, 2026 and is one of 19 known issues for this plugin.

Update, patch or deactivate.

Update to a corrected release after 3.7.8.1. Review Identity blocks with urlTransparent enabled, remove malicious inner-image content, and invalidate privileged sessions if affected pages were viewed.

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.

Technical description

The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Identity Block Inner Image Content in all versions up to, and including, 3.7.8.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only triggerable when the block's urlTransparent attribute is set to a non-empty value, as this is a required precondition for the vulnerable code path in build_html() to be reached.

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

Primary and upstream sources