CVE-2026-2924 MEDIUM

CVE-2026-2924: Gutenverse – Ultimate WordPress FSE Blocks Addons & Ecosystem <= 3.4.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'imageLoad'

Vendor Jegstudio
Product Gutenverse – Ultimate WordPress FSE Blocks Addons & Ecosystem
Weakness CWE-79 · XSS
Published April 4, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Gutenverse – Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'imageLoad' parameter in versions up to, and including, 3.4.6 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.

Explanation of Vulnerability in Simple Terms

02Summary

Gutenverse versions up to 3.4.6 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site visitors, including administrators. The vulnerability affects the plugin's block editor functionality and can impact site integrity and user data.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers, potentially stealing data or performing actions as those users.

Potential impact on your site

04Site Impact

Authenticated users can inject persistent malicious code affecting all site visitors. Administrators and other users are at risk of session hijacking or credential theft.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., contributor or editor role). No user interaction required from victims.

Key dates

06Disclosure timeline

April 4, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE