CVE-2026-6394 MEDIUM

CVE-2026-6394: Nexa Blocks <= 1.1.1 - Unauthenticated Blind Server-Side Request Forgery via 'demo_json_file' Parameter

Vendor Wpdive
Product Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Weakness CWE-918 · SSRF
Published May 20, 2026
Last update May 20, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to and including 1.1.1. This is due to the import_demo() function accepting a user-supplied URL in the demo_json_file POST parameter and passing it directly to wp_remote_get() without any URL validation or restriction against internal or private network destinations. The nexa_blocks_nonce required for the AJAX action is publicly exposed in the HTML source of any frontend page where the plugin is active via wp_localize_script on the enqueue_block_assets hook, effectively making the nonce available to all visitors and bypassing any intended authentication barrier. This makes it possible for unauthenticated attackers to make server-side HTTP requests to arbitrary internal or external destinations, potentially exposing internal services, cloud metadata endpoints such as the AWS instance metadata service, localhost services, and other resources not intended to be publicly accessible. A secondary SSRF vector also exists whereby image URLs extracted from the attacker-controlled JSON response are subsequently fetched via a second wp_remote_get() call, allowing chained exploitation through a crafted JSON payload.

Explanation of Vulnerability in Simple Terms

02Summary

Nexa Blocks versions up to 1.1.1 contain a server-side request forgery vulnerability that allows an attacker to make the site send HTTP requests to internal or external systems on the attacker's behalf. The vulnerability requires specific network conditions to exploit but can leak sensitive information or modify data on systems the site can reach. No user interaction is required.

What an attacker can do

03Attacker Capabilities

Make your site send HTTP requests to internal systems or external servers to read or modify data.

Potential impact on your site

04Site Impact

Attackers could access internal services, leak credentials, or modify data on systems your site can reach.

Conditions required to exploit

05Prerequisites

Network access to the site; specific network conditions must be present (high attack complexity).

Key dates

06Disclosure timeline

May 20, 2026 CVE published
May 20, 2026 Record updated