HomeWordPress vulnerabilitiesGutenverse
Gutenverse vulnerabilities
Gutenverse has 11 known vulnerabilities in this database. The most recent published record is dated 25 Sep 2026.
- Known vulnerabilities
- 11
- Active installs
- 20,000+
- Latest version
- 4.0.9
- Last updated
- 24 Sep 2026
- Most recent
- 25 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-92746 | Medium 6.4 | Up to 4.0.8 | Fixed in a later version (latest 4.0.9) | 12 d ago |
| Cross-site scripting (XSS) CVE-2026-3002 | Medium 6.4 | Up to 4.0.2 | Fixed in a later version (latest 4.0.9) | 26 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-19943 | Medium 6.4 | Up to 4.0.2 | Fixed in a later version (latest 4.0.9) | 25 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-12399 | Medium 4.4 | Up to 3.8.0 | Fixed in a later version (latest 4.0.9) | 27 Jun 2026 |
| Cross-site scripting (XSS) CVE-2026-3001 | Medium 6.1 | Up to 3.4.6 | Fixed in a later version (latest 4.0.9) | 27 May 2026 |
| Server-side request forgery (SSRF) CVE-2026-2948 | Medium 6.4 | Up to 3.5.3 | Fixed in a later version (latest 4.0.9) | 5 May 2026 |
| Cross-site scripting (XSS) CVE-2026-2868 | Medium 6.4 | Up to 3.5.3 | Fixed in a later version (latest 4.0.9) | 5 May 2026 |
| Cross-site scripting (XSS) CVE-2026-2924 | Medium 6.4 | Up to 3.4.6 | Fixed in a later version (latest 4.0.9) | 4 Apr 2026 |
| Cross-site scripting (XSS) CVE-2025-7727 | Medium 6.4 | Up to 3.1.0 | Fixed in a later version (latest 4.0.9) | 6 Aug 2025 |
| Cross-site scripting (XSS) CVE-2025-2893 | Medium 6.4 | Before 3.0.0 | Fixed in 3.0.0 | 29 Apr 2025 |
| Cross-site scripting (XSS) CVE-2024-3692 | Medium 6.1 | Before 1.9.1 | Fixed in 1.9.1 | 3 May 2024 |
Read the published descriptions
- CVE-2026-92746, 25 Sep 2026
- 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. CVE record
- CVE-2026-3002, 26 Aug 2026
- The Gutenverse - Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the multiple blocks in all versions up to, and including, 4.0.2 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. CVE record
- CVE-2026-19943, 25 Aug 2026
- The Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'titleTag' Block Attribute in all versions up to, and including, 4.0.2 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. The malicious titleTag value survives wp_kses_post on save because it is stored inside a block-comment delimiter and the live HTML is only synthesized at render time by do_blocks(), meaning the payload also fires in administrator and editor sessions during post preview. CVE record
- CVE-2026-12399, 27 Jun 2026
- 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. CVE record
- CVE-2026-3001, 27 May 2026
- The Gutenverse plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 3.4.6 due to insufficient input sanitization and output escaping. Specifically, the `render_content()` method in `class-search-result-title.php` outputs the value of `get_query_var('s')` directly into the page HTML without applying `esc_html()` or any other escaping function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages via a crafted URL that execute if a user clicks the link, provided the `gutenverse/search-result-title` block is present on the site's search results template. CVE record
- CVE-2026-2948, 5 May 2026
- The Gutenverse - Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 3.5.3 via the import_images() function. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. CVE record
- CVE-2026-2868, 5 May 2026
- The Gutenverse - Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'separatorIconSVG' parameter in versions up to, and including, 3.5.3 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. CVE record
- CVE-2026-2924, 4 Apr 2026
- 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. CVE record
- CVE-2025-7727, 6 Aug 2025
- The Gutenverse plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Animated Text and Fun Fact blocks in all versions up to, and including, 3.1.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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. CVE record
- CVE-2025-2893, 29 Apr 2025
- The Gutenverse - Ultimate Block Addons and Page Builder for Site Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's countdown Block in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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. CVE record
- CVE-2024-3692, 3 May 2024
- The Gutenverse WordPress plugin before 1.9.1 does not validate the htmlTag option in various of its block before outputting it back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks CVE record
What to do if you run Gutenverse
If you run Gutenverse, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Gutenverse vulnerabilities
Free. We email you when a new vulnerability is published for Gutenverse, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.