What is the CVSS score of CVE-2026-10586?

CVE-2026-10586 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Essential Blocks are affected by CVE-2026-10586?

The Essential Blocks WordPress plugin (versions ≤6.1.3) contains a server-side request forgery vulnerability that allows authenticated users with Author-level access to coerce the WordPress server…

How to fix or mitigate CVE-2026-10586?

Within 24 hours: Inventory all WordPress instances and identify those running Essential Blocks through version 6.1.3 using vulnerability scanning or plugin audit tools. Within 7 days: Since no vendor patch is available, implement compensating controls including strict Author-level access restrictions (audit all current Author accounts), disable the save_ai_generated_image() function or remove Essential Blocks if unused, and configure network segmentation to restrict outbound HTTP traffic from WordPress servers. Within 30 days: Monitor vendor advisories for patch availability and establish upgrade procedures; conduct internal review of what Author accounts accessed between current date and vulnerability awareness date.

Essential Blocks CVE-2026-10586

EUVD-2026-34771 HIGH

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

2026-06-05 security@wordfence.com

GHSA-5rm6-jpq7-cq95

WordPress SSRF

7.2

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.2 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 00:30 vuln.today

CVE Published

Jun 05, 2026 - 00:16 nvd

HIGH 7.2

DescriptionCVE.org

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.

AnalysisAI

Server-Side Request Forgery in the Essential Blocks WordPress plugin (versions through 6.1.3) allows authenticated users with Author-level access or higher to coerce the WordPress server into making arbitrary outbound HTTP requests via the save_ai_generated_image() function. The flaw enables attackers to probe internal network services, read responses from internal endpoints, and potentially modify state on services that trust requests from the WordPress host. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.

Technical ContextAI

Essential Blocks is a popular Gutenberg block library plugin for WordPress that adds page-builder style blocks and AI-assisted features. The vulnerable code path is includes/Integrations/AI/AI.php at line 171, where save_ai_generated_image() accepts a user-supplied URL and fetches it server-side without sufficient destination validation. This is a textbook CWE-918 (Server-Side Request Forgery): the server acts as a confused deputy, making outbound requests on behalf of a partially trusted user toward attacker-chosen targets, which on cloud-hosted sites commonly includes loopback services, metadata endpoints such as 169.254.169.254, and internal LAN ranges.

RemediationAI

No vendor-released patch identified at time of analysis from the provided references; administrators should monitor the Essential Blocks changelog on WordPress.org and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/08906577-162c-4875-b16c-18d4912c2611) for a fixed release above 6.1.3 and upgrade immediately when published. Until a patched version is available, compensating controls include temporarily deactivating the Essential Blocks plugin if AI image generation is not in use, restricting Author and higher role assignments to fully trusted users, and enforcing egress filtering from the WordPress host to block requests to RFC1918 ranges, 127.0.0.0/8, and cloud metadata endpoints such as 169.254.169.254 - note that egress filtering may break legitimate integrations that call internal APIs, and disabling the plugin will remove all Essential Blocks content from rendering. A web application firewall rule that blocks requests to the relevant admin-ajax/REST endpoint invoking save_ai_generated_image() with non-allowlisted URL parameters is a more surgical option.