CVE-2026-10586

Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns <= 6.1.3 - Authenticated (Author+) Server-Side Request Forgery

2026-06-04 10:40
Shambles

Strategic Overview

Status
Patched in 6.1.4
Affected Plugin
Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns
Affected Version
<= 6.1.3
CVSS
7.2High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-10586
View all Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns vulnerabilities

At a glance

CVE-2026-10586 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Gutenberg Essential Blocks WordPress plugin, affecting versions <= 6.1.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.4; sites on affected versions should update now. Disclosed June 2026, reported by Shambles.

Vulnerability Overview

The Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.1.3 via the `save_ai_generated_image()` function. This makes it possible for authenticated attackers, with Author-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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Gutenberg Essential Blocks <= 6.1.3 carries this weakness at save_ai_generated_image(), and reaching it takes an account at Author level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Gutenberg Essential Blocks the fix is 6.1.4: builds <= 6.1.3 are affected, anything from 6.1.4 onward is not.

Remediation

Update to version 6.1.4, or a newer patched version

How does WordSec protect against this?

An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gutenberg Essential Blocks 6.1.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-10586https://www.wordfence.com/threat-intel/vulnerabilities/id/08906577-162c-4875-b16c-18d4912c2611https://nvd.nist.gov/vuln/detail/CVE-2026-10586

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C