EUVD-2026-39959
GHSA-pgr2-vvf9-xmqw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as editor-level WordPress user
-
DeliveryInject script via Gutenverse admin settings field
-
ExploitPayload stored in database without sanitization
-
ExecutionVictim loads affected page on multi-site or restricted-HTML site
-
PersistMalicious script executes in victim browser
-
ImpactSession token or credential exfiltration
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 three concurrent conditions: (1) the attacker must hold an authenticated WordPress account with editor-level permissions or higher - unauthenticated or subscriber/contributor-level access is insufficient; (2) the target WordPress installation must be configured as a multi-site network OR must have the unfiltered_html capability explicitly disabled (non-default configuration); and (3) the victim must subsequently load a page where the injected payload is rendered. Standard single-site WordPress installations with default capability configuration are entirely unaffected. The limiting factors - mandatory editor authentication combined with a specific non-default deployment mode - substantially reduce the realistic attacker population compared to what the network-accessible attack vector might suggest. |
| Impact | The official CVSS 3.1 score of 4.4 (Medium) with vector AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N accurately reflects the constrained real-world impact. AC:H is warranted because exploitation requires one of two specific non-universal deployment conditions: a WordPress multi-site network or a site with unfiltered_html explicitly disabled. PR:H confirms that editor-level (or higher) authentication is mandatory, substantially limiting the attacker pool to trusted or compromised internal accounts. S:C (Scope Changed) captures that a successful injection crosses from the editor's session context to arbitrary site visitors' browsers. No KEV listing exists and no public exploit code has been identified, placing this in the lowest exploitation urgency tier. The most realistic risk is a compromised or malicious editor account using this to escalate impact against administrators or harvest visitor sessions. For most standard single-site WordPress deployments with default unfiltered_html settings, this vulnerability does not apply at all. |
| Exploit ScenarioDerived | A threat actor with a compromised or insider editor-level WordPress account on a multi-site installation injects a malicious JavaScript payload into a Gutenverse admin settings field - for example a global variable or API-controlled style setting processed through class-global-variable.php or class-api.php. The payload is stored in the database without sanitization and rendered to every visitor who loads an affected page, enabling session cookie theft, credential phishing overlay injection, or redirection to attacker-controlled infrastructure. No public proof-of-concept code has been identified, but the Wordfence advisory and multiple Trac source references provide sufficient technical detail for a skilled attacker to reconstruct the exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 27, 2026
Stored Cross-Site Scripting in the Gutenverse WordPress Blocks, Page Builder & Site Editor plugin (all versions through 3.8.0) enables authenticated editor-level users to persist arbitrary JavaScript into pages served to any site visitor. The vulnerability is constrained to WordPress multi-site installations or single-site deployments where unfiltered_html has been explicitly disabled. No public exploit has been identified at time of analysis, and a upstream fix commit (changeset 3578328) has been published to the WordPress plugin repository.
RemediationAI
Upstream fix commit (changeset 3578328 at https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3578328%40gutenverse&new=3578328%40gutenverse) has been published to the WordPress plugin repository; update Gutenverse to the version incorporating this changeset as soon as it is tagged and available via the WordPress plugin updater. The exact released patched version number is not independently confirmed from available data - verify via the plugin changelog before updating. As a compensating control where immediate patching is not possible: restrict editor-level role assignment to fully trusted accounts, as this is the minimum privilege required for exploitation. On multi-site networks, consider auditing network admin settings for unexpected changes. Sites where unfiltered_html is disabled as a deliberate hardening measure should treat this as a higher-priority update since that configuration is precisely the one that enables the attack path; re-enabling unfiltered_html as a workaround would eliminate the vulnerability condition but reintroduce broader HTML injection risk and is not recommended.
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
Gutenverse (CPE: cpe:2.3:a:jegstudio:gutenverse_-_wordpress_blocks,_page_builder_&_site_editor:*:*:*:*:*:*:*:*) is a Gutenberg-based WordPress page builder plugin. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically insufficient input sanitization and output escaping in admin-facing settings handlers. Vulnerable code paths span at least five files identified via Wordfence and WordPress Trac references: helper.php (lines 1440 and 1775), class-api.php (line 1956), class-global-variable.php (line 78), and class-frontend-generator.php (line 147). These files collectively handle global variable registration, API endpoint processing, and frontend page generation - meaning attacker-controlled data flows from settings input through storage and is later reflected to page visitors without adequate escaping. WordPress normally prevents editors from injecting unfiltered HTML via the unfiltered_html capability, but this plugin bypasses that protection through its own settings pipeline.
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:H/PR:H/UI:N/S:C/C:L/I:L/A:N
Editor auth (PR:H) and deployment-specific conditions (AC:H) required; victim page visit needed (UI:R); scope changes to visitor browsers (S:C).
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.8.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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
Exploit-DB