Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged authenticated account
-
DeliveryInject script into vulnerable Kadence block field
-
ExploitPayload stored unsanitized
-
ExecutionAdmin views affected content
-
PersistScript executes in admin browser context
-
ImpactSession/privilege compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress account with low privileges (CVSS PR:L - typically a content-contributing role such as contributor or author that can submit block content) on a site running Gutenberg Blocks by Kadence Blocks up to and including version 3.8.0.1. The stored payload only executes when another user views the injected content (CVSS UI:R), so a separate victim interaction - generally a higher-privileged user such as an administrator rendering the affected page - is needed to trigger impact. The specific vulnerable block, field, or parameter is not described in the available sources. Limiting factors: the need for a pre-existing authenticated account substantially reduces exposure on single-admin or tightly controlled sites, and the user-interaction dependency means no impact occurs until the stored content is viewed. |
| Impact | This is a moderate-severity stored XSS (CVSS 6.5, CWE-79) in the Kadence Blocks WordPress plugin, reported by Patchstack. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L indicates network-reachable but not fully unauthenticated exploitation: PR:L requires the attacker to already hold a low-privileged authenticated account, and UI:R means a victim (typically a higher-privileged user such as an administrator) must view the injected content for the payload to fire. The S:C (scope change) reflects that injected script executes in the victim's browser context, outside the component that stored it. No EPSS probability is provided in the input, there is no CISA KEV listing, and no verified working exploit code is referenced - the only reference is the Patchstack advisory itself. The vuln.today decision label is 'this_month' rather than act_now/emergency, consistent with an authenticated, user-interaction-dependent XSS rather than a wormable or mass-exploitable flaw. Net assessment: a real but second-tier priority - genuinely exploitable in multi-author WordPress environments where lower-privileged users can inject content, but gated by both an authenticated account and victim interaction, so not a drop-everything emergency. Missing EPSS and absence of KEV are notable gaps but do not change the triage conclusion. |
| Exploit ScenarioDerived | An attacker holding a low-privileged authenticated account (e.g. contributor or author) on a WordPress site running Kadence Blocks injects a malicious script payload into a block field that is not properly sanitized. The payload is stored and later rendered when a higher-privileged user, such as an administrator, views the affected page in the dashboard or on the front end, executing attacker-controlled JavaScript in that user's session. No verified working exploit code is referenced in the available sources, only the Patchstack advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Stored cross-site scripting in the WordPress plugin Gutenberg Blocks by Kadence Blocks (versions through 3.8.0.1) lets a low-privileged authenticated user persist script-bearing content that executes in another user's browser when that content is rendered. Per the assessed vector (CVSS 6.5, AV:L/AC:L/PR:L/UI:R/S:C), an attacker must already hold a content-contributing account such as contributor or author, and impact only materializes when a separate victim - typically a higher-privileged user viewing the affected page - loads the injected content. The issue was reported by Patchstack and is scheduled for this-month remediation priority; no public exploit code or active exploitation (CISA KEV) is associated with it at time of analysis, though successful exploitation crosses a privilege boundary (scope change) and can yield limited confidentiality, integrity and availability effects.
RemediationAI
No vendor-released patch or fixed version is identified in the available data at time of analysis, so the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/kadence-blocks/vulnerability/wordpress-gutenberg-blocks-by-kadence-blocks-plugin-3-8-0-1-cross-site-scripting-xss-vulnerability?_s_id=cve) should be monitored for the corrected release and the plugin updated as soon as one is published, since applying the vendor update is the only complete fix. In the interim, the exposure is governed by the assessed prerequisites: exploitation requires an authenticated low-privileged account that can submit block content, so restricting contributor and author roles on sites running Kadence Blocks to accounts that genuinely need them reduces the number of possible injection sources, at the cost of editorial workflow flexibility. Because the payload is stored and executes only when another user views the affected content (UI:R), auditing existing posts and reusable blocks for injected markup and removing suspicious block attributes limits the chance of a privileged administrator triggering a previously planted payload; this cleanup is manual and must be repeated for content created before the restriction is applied. No public exploit code is identified for this issue, and no further vendor-stated workaround is documented in the available sources.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-79, improper neutralization of input during web page generation, in a WordPress block plugin that ships Gutenberg block types for the block editor. Because block content authored in the editor is stored in the WordPress database and re-rendered on every page view, a failure to sanitize or escape one of the block's stored attributes produces persistent (stored) rather than reflected XSS: the payload survives the authoring session and fires for each subsequent viewer. The assessed vector marks scope as changed (S:C), consistent with script executing in the context of the WordPress front end or admin pages rather than the injecting user's own session, and UI:R reflects that execution depends on a victim loading the affected content. The CPE identifier cpe:2.3:a:liquid_web_/_stellarwp:gutenberg_blocks_by_kadence_blocks:*:*:*:*:*:*:*:* maps the affected codebase to the Liquid Web / StellarWP published plugin. The available sources do not identify the specific vulnerable block, attribute, or parameter, and do not describe the exact rendering path or triggering input, so the precise injection point is not described in the available sources.
Know when Gutenberg Blocks By Kadence Blocks gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
Authenticated low-privileged user stores the payload (PR:L) and a victim must render it (UI:R); script runs cross-context (S:C) with limited C/I/A impact typical of stored XSS.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
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.8.0.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Stored cross-site scripting in the Kadence Blocks WordPress plugin (Gutenberg Blocks by Kadence Blocks, versions from n/
Sensitive data exposure in the Gutenberg Blocks by Kadence Blocks WordPress plugin (versions <= 3.7.8) allows authentica
EUVD-2026-109711
GHSA-ggvv-hrvx-479f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB