WordPress security changelog
MEDIUM CVE-2026-6394 Deferred

Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE: Server-side request forgery

Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE is affected by server-side request forgery. The vulnerable path is reachable without authentication. The vulnerable server can be induced to make attacker-selected network requests. The published affected range is <= 1.1.1.

CVE / CNA score 5.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Plugin slug
nexa-blocks
Affected
<= 1.1.1
Safe version
> 1.1.1
Published
May 20, 2026
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published May 20, 2026 and is one of 5 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE to a release after 1.1.1, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

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

References

Primary and upstream sources