CVE-2026-131790 in Gutenberg Blocks by Kadence Blocks Plugininfo

Summary

by MITRE • 11/22/2026

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP Gutenberg Blocks by Kadence Blocks kadence-blocks allows Stored XSS.This issue affects Gutenberg Blocks by Kadence Blocks: from n/a through 3.9.1.1.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The identified security flaw represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this vulnerability is classified under the CWE-79 standard and manifests within the Gutenberg Blocks ecosystem developed by Kadence Blocks for WordPress environments. The affected software range spans from initial releases up through version 3.9.1.1 distributed via Liquid Web and StellarWP channels. This particular implementation of Cross-Site Scripting is categorized as Stored XSS, which distinguishes it from reflected variants by persisting the malicious payload within the application's data store rather than transmitting it solely through a single HTTP request.

In a stored XSS scenario, an attacker injects executable JavaScript code into input fields that are subsequently saved to a database or file system without adequate sanitization. When other users or administrators access pages containing this compromised content, the browser interprets and executes the embedded script as part of the legitimate page load process. This mechanism allows the malicious code to operate within the security context of the trusted website domain, effectively bypassing same-origin policy protections that typically isolate web applications from external threats. The vulnerability arises because the application fails to properly validate or encode user-supplied input before rendering it in HTML output contexts where scripts can be executed.

The operational impact of this Stored XSS vulnerability is significant due to its persistent nature and broad exposure potential. Once a malicious payload is stored, every visitor who views the affected page becomes a potential target for exploitation without requiring any additional interaction from the attacker beyond the initial injection. This persistence amplifies the risk profile considerably compared to reflected XSS attacks which require social engineering tactics like phishing links to trigger execution against specific individuals. Attackers can leverage this capability to steal session cookies, hijack administrative accounts, deface websites by altering visual content, or redirect users to malicious third-party sites designed for further exploitation such as malware distribution or credential harvesting campaigns.

From a threat intelligence perspective aligned with the MITRE ATT&CK framework, this vulnerability facilitates techniques associated with Client-Side Scripting Injection and potentially Credential Access through Browser Session Hijacking if session tokens are accessible via JavaScript APIs like document.cookie. The ability to execute arbitrary scripts in an administrative context could also lead to broader system compromise depending on the privileges of users who view or manage the compromised content within the WordPress dashboard environment.

Mitigation strategies must prioritize immediate remediation by updating the Kadence Blocks plugin to a version later than 3.9.1.1 where input sanitization and output encoding mechanisms have been strengthened according to modern web security standards. Administrators should ensure that all dependencies within their WordPress installation are current, as outdated plugins often serve as entry points for automated scanning tools employed by threat actors. Implementing Content Security Policy headers can provide an additional layer of defense by restricting the sources from which scripts may be loaded or executed, thereby mitigating the impact even if a vulnerability is present. Furthermore, adopting strict input validation practices that whitelist acceptable characters and encode special HTML entities before rendering user-generated content remains essential for preventing similar injection flaws in future development cycles.

Responsible

Patchstack

Reservation

11/17/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!