Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account
-
DeliveryInsert Google Map block with scripted marker title/content
-
ExploitSave page storing payload as JSON
-
ExecutionVictim loads page, frontend decodes marker into raw HTML
-
ImpactScript executes in victim browser session
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 | Requires an authenticated account with Contributor-level privileges or higher on the target WordPress site, and the site must use the Essential Blocks plugin (≤6.4.5) with the Google Map block available in the editor. The attacker inserts a Google Map block and injects script into a marker's title/content attribute; exploitation succeeds without any special non-default configuration beyond having the block placed on a published/previewable page. The limiting factor is the Contributor authentication barrier - sites that do not grant low-trust users contributor roles (or lack open registration) are substantially harder to exploit. Script execution is triggered only when a user (visitor or reviewing editor) views the page containing the injected block. |
| Impact | This is a Stored XSS in a popular WordPress Gutenberg block plugin, rated CVSS 6.4 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N - network-reachable, low complexity, but requiring Contributor-level authentication (PR:L) and no attacker-side user interaction (the victim viewing the page supplies the trigger, reflected in the scope change S:C). EPSS is not provided, there is no CISA KEV listing, and no public exploit code is identified - so exploitation status is 'no public exploit identified at time of analysis'. SSVC framework data is not supplied. The realistic risk is moderate and self-limiting: the PR:L gate means an attacker must already hold a Contributor (or higher) account, which is a meaningful barrier on well-managed sites but trivially met on sites with open/self-registration granting contributor roles. The C:L/I:L/A:N impact reflects browser-context script execution (session/cookie theft, limited DOM manipulation, phishing) rather than server compromise. No signals conflict; this is a genuine-but-not-urgent issue - a confirmed, vendor-patched Medium XSS with no evidence of active exploitation, best handled via normal patch cycles with priority on sites that allow low-trust author accounts. |
| Exploit ScenarioDerived | An attacker holding a Contributor account on a target WordPress site inserts the Essential Blocks Google Map block into a draft and places a malicious script payload in a map marker's title/content field, which is stored as JSON. When any visitor or reviewing editor opens the page, the frontend InfoWindow builder decodes the JSON and concatenates the marker values directly into raw HTML, executing the script in the viewer's browser. No public proof-of-concept is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Stored cross-site scripting in the Essential Blocks - Page Builder for Gutenberg Blocks & Patterns WordPress plugin (versions up to and including 6.4.5) allows authenticated attackers with Contributor-level access or higher to inject arbitrary JavaScript that executes when a victim views the affected page. The flaw sits in the Google Map block's 'marker' attribute: marker title/content values are stored as JSON and later decoded and concatenated directly into raw HTML by the frontend InfoWindow builder, so it is insufficient input sanitization plus missing output escaping rather than a logic error. It is network-reachable at low complexity with a scope change (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4 Medium); the practical barrier is the Contributor authentication requirement, and no public exploit code was identified at time of analysis. Sites that allow open registration or grant Contributor roles to low-trust users should treat this as a priority upgrade.
RemediationAI
Vendor-released patch: 6.4.6. Upgrade the Essential Blocks plugin to version 6.4.6 or later immediately - the Trac changeset (new=3715353@essential-blocks/tags/6.4.6, old=3706819@essential-blocks/tags/6.4.5) shows the fix, which reworks the Google Map marker rendering in assets/blocks/google-map/frontend.js and the associated save/render paths to stop concatenating untrusted marker values into InfoWindow HTML. Until upgrade is possible, reduce exposure by removing or disabling the Google Map block from the editor for non-trusted roles, or by restricting who can create or publish content containing that block; note that this degrades editor functionality and requires a role/permission change or an editor-level block restriction, so it must be coordinated with site editors. Where the site cannot upgrade promptly, strip the Contributor role from untrusted or self-registered users and audit existing posts and revisions for any Google Map block whose marker title/content contains markup, since payloads persist in post content and will keep firing after patching until the stored data is cleaned. Reviewing the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/606f25d9-f8c7-416a-8bb8-0cc57901ff5a?source=cve is recommended for the vendor's own remediation guidance. Because the injection is stored rather than reflected, blocking or filtering inbound requests alone does not remove already-persisted payloads.
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 vulnerability is a classic CWE-79 improper neutralization of input during web page generation, manifesting in the WordPress Gutenberg block editor ecosystem. The affected component is the plugin's Google Map block, a dynamic block whose marker data (title and content) is serialized into the post content as JSON. Per the referenced source, save.js (line 35) handles the block's save/serialization path, GoogleMap.php (line 82) handles the server-side block registration and rendering, and assets/blocks/google-map/frontend.js (line 1) is the frontend script that decodes the stored JSON and builds the Google Maps InfoWindow content string by concatenation rather than by assigning textContent or escaping entities. Because that concatenated string is inserted as raw HTML into the InfoWindow DOM, an attacker-supplied marker title or content containing script markup or event-handler attributes is parsed as HTML and executed in the origin of the affected site when any user opens the page. The identical code paths are present in the 6.3.0 tag as well as 6.4.5, indicating the weakness persisted across a broad version range rather than being a regression in a single release. Scope is assessed as changed (S:C) because the injected script executes in the context of the WordPress site's pages and can act on behalf of the viewing user, including higher-privileged editors or administrators who preview or moderate the containing post.
Know when Wordpress Plugin 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:N/S:C/C:L/I:L/A:N
Network-reachable stored XSS requiring a Contributor account (PR:L), executing in a different victim's browser context (S:C) with limited confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Gutenberg Essential Blocks - Page Builder for Gutenberg Blocks & Patterns plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Google Map block's 'marker' attribute in versions up to, and including, 6.4.5 This is due to insufficient input sanitization and output escaping on marker title/content values, which are stored as JSON and then decoded and concatenated directly into raw HTML by the frontend script's InfoWindow content builder. 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.
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.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-90594
GHSA-5chw-2jmg-373v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB