Skip to main content

Gutenverse EUVDEUVD-2026-86547

| CVE-2026-92746 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-25 Wordfence GHSA-q95q-8hph-jj29
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain contributor account
  2. Delivery
    Insert Post Comment Block with script in suffixMain
  3. Exploit
    Save post storing payload in block delimiter
  4. Execution
    Victim loads page, PHP renders payload
  5. Impact
    Script executes in victim browser, session hijack

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 capability or above on a WordPress site running Gutenverse <=4.0.8, and the attacker must be able to add/edit a Post Comment Block (default capability for contributors who can create posts). The payload is injected via the block's 'suffixMain' attribute and stored within a Gutenberg block-delimiter comment; standard WordPress wp_kses_post sanitization does NOT neutralize it because it is only converted to live HTML at the PHP render stage. Limiting factors: exploitation is gated on the site permitting contributor-level (untrusted) authors - single-admin sites have little exposure - and payload execution is deferred until a victim views the affected page.

Impact

This is a genuine but moderate-priority issue, not a critical one. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4) accurately reflects a low-privilege authenticated stored XSS with changed scope: an attacker needs only contributor-level access, no user interaction to plant the payload, and execution crosses a security boundary (attacker's stored content runs in a victim's browser session), justifying S:C and the C:L/I:L partial impacts. No EPSS score, no CISA KEV listing, and no public POC were supplied, so exploitation status is 'no public exploit identified at time of analysis' - this is not evidence of active exploitation. There is no SSVC decision data in the input; on its own merits the flaw is not automatable (requires an authenticated contributor account per target site) and technical impact is partial rather than total. The most important nuance, well-documented in the description, is that this bypasses WordPress core wp_kses_post sanitization because the payload lives inside a Gutenberg block-delimiter comment and is only materialized as HTML at the PHP render stage - meaning defenders relying on core sanitization gain no protection. No signals conflict; the CVSS is consistent with the described mechanism. Bottom line: prioritize patching on multi-author sites where untrusted contributors exist, but this is not a mass-exploitation, network-unauthenticated emergency.

Exploit ScenarioDerived

An attacker who has obtained (or been granted) a contributor account on a WordPress site running Gutenverse <=4.0.8 inserts a Post Comment Block and places a malicious script payload in the block's 'suffixMain' attribute, which is saved inside the block-delimiter comment and survives wp_kses_post. When an administrator, editor, or visitor later views the page, the script is rendered as HTML at the PHP render stage and executes in their browser, enabling session/cookie theft or actions in the victim's context. No public exploit code is identified at time of analysis, and exploitation requires the attacker to already hold contributor-level access.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Stored cross-site scripting in the Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin (all versions up to and including 4.0.8) lets an authenticated attacker holding contributor-level access or above inject arbitrary JavaScript through the Post Comment Block's 'suffixMain' attribute, which is written into a Gutenberg block-delimiter comment and only converted into live HTML when the block is rendered server-side in PHP. The stored script then executes in the browser of any user who views the affected page, scoring CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) because exploitation crosses the block-content trust boundary even though the injected account is only a low-privileged author. Exposure is gated on the site actually granting contributor-level publishing rights and on a victim later visiting the poisoned page; no public exploit code was identified at time of analysis and the flaw is not confirmed as actively exploited (not listed in CISA KEV), which positions this as a genuine but moderate-priority issue rather than a critical one.

RemediationAI

There is no vendor-tagged patched release confirmed in the available data; the most specific fix signal is an upstream commit to plugin trunk recorded as WordPress plugin Trac changeset 3710420 (https://plugins.trac.wordpress.org/changeset/3710420/gutenverse/trunk/includes/block/class-post-comment.php), so treat this as upstream fix available (PR/commit) with a released patched version not independently confirmed and upgrade to the first plugin release newer than 4.0.8 as soon as it ships. Until then, the highest-value compensating control is reducing privilege: remove or restrict the contributor role on affected sites (Author/Contributor accounts that cannot be trusted) since exploitation requires contributor-level capability or above, accepting the editorial workflow impact this causes. If contributors must remain, disable or unregister the Post Comment Block (for example via a plugin that filters allowed block types, or by removing the block from the block registry) so the 'suffixMain' attribute sink cannot be reached, understanding that any pages already containing Post Comment Blocks may render inconsistently. Sites that cannot do either should convert untrusted contributor accounts to a submission-review workflow where an administrator with unfiltered_html inspects block markup before publication, and should treat existing posts containing Post Comment Blocks as potentially poisoned and review or re-save them. Monitor the plugin's changelog and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/e35f9e09-c386-4e37-9d81-8dd2863457ac?source=cve for the patched version number, and note that a web application firewall rule targeting block-delimiter attributes in stored content may partially mitigate but will not fix the underlying defect.

Affected VersionsENISA

Gutenverse – WordPress Blocks, Page Builder & Site Editor 0 ≤4.0.8

Affected Packages

euvd gutenverse_wordpress_blocks_page_builder_site_editor no fix

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, but with an unusual storage path that defeats WordPress's usual defenses. Gutenberg blocks are persisted as HTML comments (block delimiters such as <!-- wp:gutenverse/post-comment {...} /-->) whose JSON attributes travel alongside the markup; the 'suffixMain' attribute of the Post Comment Block is not sanitized on input nor escaped on output, so attacker-controlled text survives inside the delimiter comment. WordPress's wp_kses_post filter does not help here because the payload is never a raw HTML tag at save time - the comment content is inert during storage and only reinserted into the DOM as executable HTML at the PHP render stage inside includes/block/class-post-comment.php (see Trac references to lines 51 and 80 of the 4.0.8 tag). The CPE cpe:2.3:a:jegstudio:gutenverse_-_wordpress_blocks,_page_builder_&_site_editor:*:*:*:*:*:*:*:* covers the whole plugin line, and because the sink is server-side render output, normal client-side block validation does not catch it either. The CVSS vector's PR:L is accurate - the actor needs a contributor account whose default capability already permits creating posts with blocks - while S:C reflects that the injected script executes in the security context of other users viewing the page rather than the author's own.

Know when PHP 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

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Contributor account gives PR:L; storing the payload needs no victim interaction (UI:N); XSS crosses into victims' browser context (S:C) with partial confidentiality/integrity impact and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Post Comment Block 'suffixMain' Attribute in all versions up to, and including, 4.0.8 due to insufficient input sanitization and output escaping. 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. WordPress core wp_kses_post sanitization does not mitigate this vulnerability because the payload is stored inside a Gutenberg block delimiter comment rather than as a raw HTML tag, and is only rendered as exploitable HTML at the PHP render stage.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche third-party WordPress page builder plugin, modest install base
Data Quality
3 sources
Confidence: Low

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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 PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy