Essential Blocks EUVD-2026-39164

Exploitation requires a valid WordPress account with at minimum Contributor-level privileges on the target installation - this is the binding prerequisite confirmed by the CVSS PR:L metric. The attacker must be able to create or edit content blocks using the Essential Blocks plugin and specifically place a Table of Contents block with a manipulated configurablePrefix attribute value. Payload execution is deferred: it occurs when any other user (authenticated or unauthenticated, depending on page visibility settings) loads the post or page containing the injected block. Sites that restrict the Contributor role to vetted, trusted users are substantially protected. Sites with disabled user registration and no external contributors have near-zero attack surface. The vulnerability is scoped to the Table of Contents block's configurablePrefix attribute specifically - sites using Essential Blocks exclusively for other block types are not exposed through this vector. There is no exploitation pathway for unauthenticated users to inject the payload.

The CVSS 6.4 score reflects a Scope:Changed impact, acknowledging that the vulnerability's effect crosses the boundary from the WordPress application into victims' browser contexts - a meaningful elevation beyond typical low-privilege content injection. The primary risk amplifier is the PR:L (Contributor-level) access requirement: on WordPress sites with open user registration, multi-author teams, or untrusted contributor pools, any registered user can weaponize this flaw without further escalation. EPSS score is absent from available data, so exploitation probability cannot be quantified; the KEV listing is likewise absent, meaning active exploitation is not confirmed at this time. However, Wordfence's public disclosure and the presence of specific source file and line number references on WordPress Trac effectively make the vulnerability trivially locatable for exploit developers, narrowing the gap between disclosure and exploitation. The CVSS AC:L (Low complexity) confirms no special race condition or environmental quirk is required. Compared to reflected XSS, the stored nature eliminates the need for victim phishing or social engineering, broadening real-world impact. The Missing EPSS data is a gap - risk escalation should be monitored if exploitation reports emerge.

A threat actor registers a Contributor account on a WordPress site running Essential Blocks 6.1.4 or earlier - achievable on any site with open registration - then creates or edits a post embedding a Table of Contents block and sets the configurablePrefix attribute to a crafted JavaScript payload. After saving the post, every visitor who loads the page, including site administrators, triggers the stored script in their browser, allowing the attacker to silently harvest session cookies, redirect users to a credential-harvesting site, or inject content impersonating the site. No public POC is referenced in current intelligence, but the vulnerability's precise location in public Trac source makes exploit authoring straightforward.